On Mon, 2004-03-08 at 01:52, Karl Fogel wrote:
> Ben Collins-Sussman <sussman@collab.net> writes:
> > We could release 1.0.1 first, and then a couple of days later tell
> > people to upgrade to apache 2.0.49... but not everybody builds apache
> > either. Maybe it's worth waiting a couple of days so that our 1.0.1
> > tarball can get a copy of the 2.0.49's apr-util. The db4.2 problem is
> > huge in my mind.
>
> Two things:
>
> No, three things:
>
> First, we should probably delay 1.0.1 a few days no matter what, just
> because we (uh, I) were a bit over-ambitious about getting all the
> changes reviewed by this weekend. Would Friday, March 12th for 1.0.1
> be okay with folks?
>
> Second, I don't think it's a good idea to ship a brand-new
> apr/apr-util in what is supposed to be a safe, conservative
> maintenance release of Subversion.
Tiny note: there has been relatively little churn in the 0.9 branch
of APR.
> Sure, probably Apache 2.0.49 will be stable and wonderful.
Ofcourse it will be! :)
> But by the time we're ready for SVN 1.0.2,
> we won't even have to say "probably" anymore -- we'll *know*, because
> 2.0.49 will have been out there for a while :-).
>
> Third, we can solve the BDB detection problem by shipping 1.0.1 with
> the patch applied to apr-util's configury (I mean the one from
> http://subversion.tigris.org/project_faq.html#linux-bdb42-build).
> Yes, this means that the apr-util in subversion-1.0.1.tar.gz will be
> *slightly* different from the officially released apr-util, but this
> is a normal technique for dealing with interim bugs in dependencies.
> As long as the patching doesn't get out of hand, it's fine.
That would fix the standalone situation, but for people building
using httpd 2.0.48's apr/apr-util, it won't help. Cliff is doing
an APR release wednesday, FWIW. Same problem, but at least you'll
be shipping an official release.
That said, I don't think we should hold up a Subversion release
for an httpd release.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 8 05:33:49 2004