Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: Version number 2.4.43 with Patch ? |
|
Author |
|
Otomatic
Joined: 01 Sep 2011 Posts: 204 Location: Paris, France, EU
|
Posted: Wed 22 Apr '20 12:48 Post subject: |
|
|
Hi,
Why not put an evolutive version number, like 2.4.43a or 2.4.43.1, this would avoid confusion and possible problems with two different versions but still named 2.4.43.
As far as I am concerned, for Wampserver, it is named 2.4.43a.
Best regards |
|
Back to top |
|
Steffen Moderator
Joined: 15 Oct 2005 Posts: 3093 Location: Hilversum, NL, EU
|
Posted: Wed 22 Apr '20 13:42 Post subject: |
|
|
We follow the official ASF HTTPD project numbering. The released source code is still 2.4.43 GA. In this case we have an agreed ASF fix/patch added and mentioned in our announcement and change log. Discussed this with AH, and Apachehaus is also not changing names.
Also we have quite a lot users that auto check for updates by looking at the file. With changing names they ar not happy. |
|
Back to top |
|
James Blond Moderator
Joined: 19 Jan 2006 Posts: 7360 Location: Germany, Next to Hamburg
|
Posted: Sat 25 Apr '20 8:21 Post subject: |
|
|
The httpd project does not follow
Code: |
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards compatible manner, and
PATCH version when you make backwards compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format. |
Otherwise the number x in 2.x.y would have to increase a lot more often |
|
Back to top |
|
|
|
|
|
|