https://bz.apache.org/bugzilla/show_bug.cgi?id=62218
Christophe JAILLET <christophe.jail...@wanadoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
OS| |All
--- Comment #1 from Christophe JAILLET <christophe.jail...@wanadoo.fr> ---
Hi,
the download area is updated just a few days after the release is made. This
time is necessary to let all mirrors get the latest files.
It will be fixed soon (but thanks for spotting it, anyway)
2.4.30 and .31 have just been release candidates and have not been officially
released.
In our release process, we basically do as follow:
- announce to the community that a new release is being prepared
- tag a version (i.e. 2.4.30)
- give a few days for PMC, developers and whoever want to test, the ability
to spot any defect before an official release
- if no negative feedback raises, the release is officially voted, and
released.
- if an issue is detected, it is not released. It has to be fixed before a
new try.
You can have a look at
http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/STATUS?view=markup.
and at the [VOTES] threads in the http-dev mailing list
(http://httpd.apache.org/lists.html#http-dev)
The case of 2.4.32 is a bit special. It has been tested, and voted for an
official release BUT an issue (related to some specific configuration in
Windows only) has been reported just a few hours after the end of the vote.
We have taken the decision to release it anyway (it was voted) but to not
announce it (a 2.4.33 was already on the way to fix this issue)
The latest stable version is 2.4.33, release on 2018-03-17.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
