With the continual feature additions in the 2.4.x series, I dare say the project fell into a versioning slump like Linux had in the 2.6.x series. Rather than being a fixed set, instead it was continually evolving, and Apache's "2.4" prefix on version numbers is effectively just as meaningless at this point.
It could probably replicate Linux's solution to this and stop fixing "major" version numbers. Make the next release 3.0, then 3.1, and so forth. And every so often, bump that first part so it's not on "3." forever either.
It could probably replicate Linux's solution to this and stop fixing "major" version numbers. Make the next release 3.0, then 3.1, and so forth. And every so often, bump that first part so it's not on "3." forever either.