> The release branch model would alternately allow us to change that > primary version to "2.0.x-alpha-1", "2.0.x-alpha-2", "2.0.x-beta-1" and > finally "2.0.x-gold". That would also be a reasonable solution. No, all that does is add two more invisible version fields to our version numbers. We already have three version numbers -- that is more than enough. What we should be doing is changing the minor number every time we change the MMN. That way we would now be on 1.32.3 instead of 1.2.22 and our panties wouldn't creep up so far every time somebody tagged a bad tree. ....Roy
- RE: cvs commit: httpd-2.0 STATUS Gonyou, Austin
- Re: cvs commit: httpd-2.0 STATUS Roy T. Fielding
- Re: cvs commit: httpd-2.0 STATUS Cliff Woolley
- Re: cvs commit: httpd-2.0 STATUS William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0 STATUS William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0 STATUS Ryan Bloom
- Re: cvs commit: httpd-2.0 STATUS William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0 STATUS Ryan Bloom
- Re: cvs commit: httpd-2.0 STATU... William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0 S... Roy T. Fielding
- Re: cvs commit: httpd-2.0 S... Ryan Bloom
- Re: cvs commit: httpd-2.0 S... William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0 STATUS Roy T. Fielding
- Re: cvs commit: httpd-2.0 STATUS William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0 STATUS William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0 STATUS Roy T. Fielding
- RE: cvs commit: httpd-2.0 STATUS Gonyou, Austin
- Re: cvs commit: httpd-2.0 STATUS Justin Erenkrantz
- Re: cvs commit: httpd-2.0 STATUS William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0 STATUS William A. Rowe, Jr.
