On 26/01/2015 22:19, Christopher Schultz wrote: > Mark, > Mark, > > On 1/26/15 2:41 PM, Mark Thomas wrote: >> On 26/01/2015 15:31, Christopher Schultz wrote: >>> Mark, >>> >>> On 1/26/15 3:31 AM, Mark Thomas wrote: >>>> On 24/01/2015 19:21, Konstantin Kolinko wrote: >>>>> 2015-01-24 13:00 GMT+03:00 <ma...@apache.org>: >>>>>> Author: markt >>>>>> Date: Sat Jan 24 10:00:32 2015 >>>>>> New Revision: 1654487 >>>>>> >>>>>> URL: http://svn.apache.org/r1654487 >>>>>> Log: >>>>>> Prep for next tag >>>>>> >>>>>> Modified: >>>>>> tomcat/tc8.0.x/trunk/build.properties.default >>>>>> tomcat/tc8.0.x/trunk/res/maven/mvn.properties.default >>>>>> tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml >>>>>> >>>>> >>>>>> Modified: tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml >>>>>> URL: >>>>>> http://svn.apache.org/viewvc/tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml?rev=1654487&r1=1654486&r2=1654487&view=diff >>>>>> ============================================================================== >>>>>> --- tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml (original) >>>>>> +++ tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml Sat Jan 24 10:00:32 >>>>>> 2015 >>>>>> @@ -44,7 +44,9 @@ >>>>>> They eventually become mixed with the numbered issues. (I.e., numbered >>>>>> issues to not "pop up" wrt. others). >>>>>> --> >>>>>> -<section name="Tomcat 8.0.18 (markt)"> >>>>>> +<section name="Tomcat 8.0.19 (markt)" rtext="in developent"> >>>>> >>>>> 1. Typo: in development >>>> >>>> Fixed. Thanks. >>>> >>>>> 2. An interesting idea, but release manager would have to remove that >>>>> text when creating a tag. If you do not mind that extra work, then an >>>>> item should be added to Release process description in the Wiki. >>>> >>>> I'll see how I get on with it. It was a spur of the moment thing so I >>>> might go off the idea. >>> >>> Assuming I'm reading that correctly, it implies that we might be >>> publishing changelogs *before* a release has actually been rolled. >> >> It is mainly there for folks that look at the file in svn or on the CI >> server. >> >>> I >>> really like this idea, if for no other reason than the changelog often >>> doesn't get updated with the latest release date until the *following* >>> release, which is ... irritating. :) >> >> No easy way to fix that. > > If we have marker text that means "in development", we can re-build the > site from svn trunk whenever we want and we can even remove the "in > development" builds if we want.
But the web site is meant to be the docs for the latest released version. What I'd really like to do is get the release date into the actual release but that requires a crystal ball as to whether or not the VOTE will pass and when. If we changed that date from "release date" to "tagged date" (or some better name) we could set the date when we do the tag - that would be a lot nicer. >>> What about having instead of "release text" or whatever, maybe an ENUM >>> which contains a few mnemonics like "dev", "release", "votefail", etc.? >>> That can be validated by an XML validator and the XSLT can produce >>> standardized text for each status. >> >> Not sure how that would help with the most important part which is the date. > > Good point. Do you not use a release script that does that for you? Nope. I do that manually as part of the version number changes when updating for the next release. (It would take me far longer to write and test a reliable script than it does to just do the update manually). Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
