I just caught up on the torrent of emails to this list. :-) My understanding of the major issues which may aid Apache2 adoption: - avoid breaking user configuration files between releases - avoid breaking 3rd party modules between releases - present clearer meaning of version numbers to those external to Apache development
At the same time, it is important to keep the Apache project fun for developers, which includes (whenever possible) not blocking developers from playing and not blocking progress of the Apache project. I had opposed a 2.1 for the auth modules because it didn't fit well with my understanding of the way Apache development worked at the time. Since we're discussing modifying the versioning of development on the whole, my choice is different. Bill's proposal goes a long way towards addressing the issues above. +1 to concurrent stable and development branches -0.5 to using odd for stable, and even for development The model of parallel stable and development branches is similar to numerous other projects, including the Linux kernel and Perl, except that the meaning of the sub-version numbers is **reversed** in Bill's proposal. While I am not saying we should copy the Linux and Perl versioning "just because", I am suggesting that it is counter-intuitive and confusing to end-users (and suits!) who are familiar with them. Therefore, I would like to see X.even == stable and X.odd == development. -Glenn
