News for hackers. Stuff that matters.
Re:Apache 2.4.17 with HTTP/2 support by vpkaihla on Friday October 16, 2015 @07:41AM (#10398647)
They added a significant new protocol in a minor upgrade. Is that right?
Re:Apache 2.4.17 with HTTP/2 support by dtech on Friday October 16, 2015 @08:00AM (#10398698)
Apache version numbering is similar to what the linux kernel used before 2.6.

In a.b.c, odd b indicates the unstable or experimental branch, and even b's are used for major and backwards-compatibility breaking changes. Backwards-compatibility preserving changed can be introduced in c.

So 2.2 and 2.4 are pretty different versions, while 2.3 and 2.4 are closer except 2.3 is unstable. 2.4.0 is theoretically compatible with 2.4.17, except the latter has a lot more functionality and features.

Re:Apache 2.4.17 with HTTP/2 support by chrisseaton on Friday October 16, 2015 @07:45AM (#10398657)
If all it does is add new functionality, and doesn't modify or break any existing functionality, then that seems to be good software engineering to do in a minor upgrade doesn't it?
Re:Apache 2.4.17 with HTTP/2 support by dtech on Friday October 16, 2015 @07:56AM (#10398681)
If you follow semantic versioning, the third number should only be used for bugfixes. They don't.
Re:Apache 2.4.17 with HTTP/2 support by dspillett on Friday October 16, 2015 @08:02AM (#10398709)
Seems valid: MAJOR.MINOR.PATCH, with the minimum changes being increment "patch" for backwards compatible bug fixes, "minor" for new/improved functionality that does not break backwards compatibility, and "major" for any API/feature change that is not backwards compatible. They could of course chosen to increment MAJOR instead, but they don't have to in this case.

(I'm assuming they are following "standard" semver rules here)

Re:Apache 2.4.17 with HTTP/2 support by dtech on Friday October 16, 2015 @08:07AM (#10398727)
They don't use semver, and their versioning scheme precedes semver.
Re:Apache 2.4.17 with HTTP/2 support by skrause on Friday October 16, 2015 @08:10AM (#10398739)
In your example MAJOR.MINOR.PATCH they actually only increased PATCH, Apache 2.4.0 was released in early 2012.
Re:Apache 2.4.17 with HTTP/2 support by dspillett on Friday October 16, 2015 @09:13AM (#10398996)
Ah, I was assuming the mention of "minor" in the post I replied to was referring to minor in the semver sense, without actually checking. My bad.
Re:Apache 2.4.17 with HTTP/2 support by ta0967 on Friday October 16, 2015 @11:12AM (#10399826)
"backwards compatible bug fixes" don't exist: fixing a bug changes the program's behavior.
Re:Apache 2.4.17 with HTTP/2 support by dspillett on Friday October 16, 2015 @11:21AM (#10399898)
Compatibility in this case is referring to published APIs and not changing documented behaviour. There are a large family of changes that are bug fixes that don't change correct use of an API - many security fixes for example.
Re:Apache 2.4.17 with HTTP/2 support by barkingcat on Friday October 16, 2015 @10:10AM (#10399369)
why wouldn't it be right? Not everyone uses semver, and apache project version #'s precedes semver by a long while.
Re:Apache 2.4.17 with HTTP/2 support by laumars on Friday October 16, 2015 @09:43AM (#10399164)
It's an optional module rather than changing the core logic (as 2.2->2.4 did), so in that regard it makes sense to only up the minor version number.
Re:Apache 2.4.17 with HTTP/2 support by marktangotango on Friday October 16, 2015 @08:18AM (#10398769)
A better title would probably be: with OPTIONAL http2 support.
Re:Apache 2.4.17 with HTTP/2 support by itsbits on Friday October 16, 2015 @07:44AM (#10398654)
not defaulted as http2 though.