Re: Release Frequency and Testing

[Robert La Ferla]

I have no problem with running release candidates and contributing.  I 
have contributed in the past by the way...  In fact, I wouldn't object 
to trying nightly or weekly builds.  The problem is that I don't see 
those as easily available from the httpd.apache.org website.  There is a 
link to the latest source tree but the source code there does not have a 
configure script.  Yes, I can build the script (autoconf?) but if you 
want people to test software on a regular basis, it would be better to 
have a ready to go source release on a nightly basis.  Perhaps, you have 
this but I couldn't find it.

There's also the issue of release frequency.  I remember seeing some 
discussion about it several releases ago but no action was taken.  More 
frequent releases would be much welcomed.  Take this recent user_track 
bug.  A lot of sites use cookie tracking.  It would be great if there 
was a release that fixed it.  In the interim, it would be nice to see 
some mention of a workaround on the site for users.

Robert

William A. Rowe, Jr. wrote:

Finally, understand that most new tests are reactions to current bugs, so
that a brand new regression of code that never 'merited' a test might not 
be caught.  So the ONLY WAY TO PREVENT THIS is to please, please,
PLEASE obtain the release candidates and use them in real situations and
production load.  Until more do so, and scream at regressions, there is
ultimately nothing we can do to avoid the sort of problem you encountered.

Bill