On 14/03/2022 16:44, Christopher Schultz wrote:
All,
The current release process as written ends up with the release-date of
the latest release not appearing in the changelog until the *following*
release is done.
I think we should change this. I have tried to remember to do it myself
with 8.5.x when I do releases.
When we have monthly releases, it's not really a huge deal. But when the
releases become less and less frequent (e.g. maintenance mode), then we
have problems like this:
https://tomcat.apache.org/tomcat-6.0-doc/changelog.html
https://tomcat.apache.org/tomcat-7.0-doc/changelog.html
https://tomcat.apache.org/tomcat-8.0-doc/changelog.html
According to those changelogs, the latest releases do not have a
release-date. But they were in fact released.
I agree it isn't perfect but how much of a problem is that?
Are there any objections to making it a policy to update those
changelogs with each actual release and not just the following release?
Interesting. Looks like we've changed the text a little over the years.
We used to say "Released yyyy-mm-dd". Now it is just "yyyy-mm-dd".
The problem with setting the release date before we tag is that we don't
know the exact date the vote will pass. 3 working days is usually a good
guess. Is it good enough (assuming the date is corrected to the actual
date if necessary)?
What if we just set it to "released" and then changed that to the actual
release date once known? Or changed it to "release yyyy-mm-dd" like we
used to.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
