> > We weren't using that anywhere. Also, keeping this means that we > > are storing revision information in two places, the > > server-string, and the REVISION macro, > > Yes, and so? 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. > > > oh, and the MMN. :-( > > Which you forgot to bump (see > http://dev.apache.org/how-to-release.html 2. Note:) If bumping the MMN is part of the release, then we are broken. The MMN should be bumped when the change is made. Otherwise, it is useless. Ryan _____________________________________________________________________________ Ryan Bloom [EMAIL PROTECTED] Covalent Technologies [EMAIL PROTECTED] -----------------------------------------------------------------------------
- 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.
- Re: cvs commit: httpd-2.0 STATUS Justin Erenkrantz
