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. Sure, probably Apache 2.0.49 will
be stable and wonderful. 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.
Regarding giving ourselves a bit more time to make 1.0.1:
It's totally my fault for suggesting an overly ambitious schedule for
the review/application of everything in STATUS. I was too optimistic
about how much code-work the Chicago developers could do between
meetings, during our visit to the Mother Ship in California last week.
We just returned this weekend, so having a couple more days for review
would be great.
(Obviously, this process doesn't truly need to block on the Chicago
developers. However, getting the changes voted on & committed early
hasn't been much of a priority for the majority of other committers.
This is not a criticism -- I was the one who proposed the Tuesday date
in the first place, and then didn't have the resources to make it
happen :-). Sorry, I'll try to be more realistic next time.)
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 8 02:42:09 2004