// From alpha to production
// ready in 2 months is something of a miracle I would have to admit
// considering the size of the project.
Well, it wasn't alpha to production, it was alpha to beta to beta to alpha
to beta to alpha to production (skipped 4 betas ther). And the first Alpha
was over 2.5 years ago.
When an alpha follows a beta, it simply
means there's been a set of changes which's been isolated for testing, and
to be tested by a select few ppl. It doesn't mean that the software is in
an unstable stage in its course of development. You could say all the kernel
-pre patches are betas and the ac/dj/aa etc. are alphas.
However, now that Apache is officially "released" for GA, the ASF has made
a commitment, using their own judgement that it is in fact stable.
That was what the release was all
about. And this time, it's straight from the developers, not from a guy
called Bob in the US who was free on a Thursday afternoon...
// (I wonder how
// much changed between 2.0.31 and 2.0.35 -
// the version number suggest
// probably next to nothing) is in a alpha stage.
If you chekc the changelog between 2.0.31 and 2.0.34 it's about 150 fixes
in all - out of which about a 100 odd are just cleanups. And most of them
have been fine-tunings.
================================================
To subscribe, send email to [EMAIL PROTECTED] with subscribe in subject header
To unsubscribe, send email to [EMAIL PROTECTED] with unsubscribe in subject header
Archives are available at http://www.mail-archive.com/ilugd%40wpaa.org
=================================================
