httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: cvs commit: apr/include apr.hw
Date Mon, 12 Feb 2001 16:11:15 GMT

> > This is what was scaring me BTW.  I have rolled three times this week, and
> > each time there has been some OS that didn't work.  The first time it was
> > OS/2, then BeOS, now Windows.  It seems to me that because we aren't
> > freezing the tree and asking people to work on stabilizing the code, we
> > are likely to continue to hit this problem.  The big problem is that we
> > have four very different platforms, and it is too easy to accidentally
> > break one when fixing another.  That is a problem, but it is a problem
> > that we aren't fixing right now, so not asking for some sort of code
> > freeze is going to continue to cause these problems IMHO.
> >
> The build breaks are a temporary problem (I hope :-) and should become less
> and less frequent over time as we eliminate OS specific code paths & include
> trees in Apache proper.  When we decide to begin driving for a beta release,
> we should freeze commits not required to get all the OSes building for
> a -short- period of time, perhaps 2 days max. Announce the intent to tag a
> beta candidate, give everyone a couple of days to get all the builds working,
> then tag and roll and unfreeze.  If you miss the window, then catch it next
> time around. "Release early & release often"!

This is not the model being used currently.  This is in fact the model I
am asking for.  What is currently being proposed however, is no code
freezes, ever.


Ryan Bloom               
406 29th St.
San Francisco, CA 94131

View raw message