Re: More on possible problem with Neon 0.25.0 [was Re: 1.3.0 RC1 ready to be rolled]

John Peacock <jpeacock@rowman.com> writes:
> Yeah, sure, for RC purposes, just throw in the code to block that one
> Neon release. For the final 1.3 release, however, we need to be more
> subtle. As pointed out, there are likely to be people out there with
> system RPM's that install 0.25.0 and they don't want to rebuild for
> some reason.

Er, I'm really not here, I'm on my way to the airport, but I wanted
to quickly mention a problem with this strategy.

The whole point of an RC is to be the same as what is finally
released, so that what we're releasing has been through a soak period.
We can't hack configure one way "for RC purposes" and then hack it
another way "for the final 1.3 release" -- that would defeat the
purpose of the RC.

-Karl

-- 
www.collab.net  <>  CollabNet  |  Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org