News for hackers. Stuff that matters.
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.