2015-01-28 11:41 GMT+03:00 Mark Thomas <ma...@apache.org>: >>>>>> 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 > [...]
>>>> 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. rtext="tagged 2015-01-28", and change it into release date or "not released" afterwards. It is possible to use both dates, but I think it looks ugly, maybe except the "not released" use case, rtext="tagged 2015-01-28, not released", rtext="tagged 2015-01-28, released 2015-02-05", rtext="tagged 2015-01-28, beta 2015-02-05", Tag dates are useful when looking into git changelog (that does not have svn tags). Release dates are used in our board reports, and generally useful for the public. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
