Hi,
Writing this on behalf of the endoflife.date project, where we recently
started tracking tomcat releases and support[0]. To track tomcat
releases automatically, we are tracking the tags on the GitHub
repository[1] which results in this data[2].
I wanted some clarification about the release process, specifically with
regards to tagging new releases. I read through the archives, and
noticed that the 10.0.23 release is still pending a vote, but it is
already tagged:
- https://github.com/apache/tomcat/releases/tag/10.0.23
Arch (and its downstream distros) seems have to have already packaged
this: https://repology.org/project/tomcat/history. Repology is already
marking 10.0.22 as an "outdated" release in this case. A similar delay
happened for 9.0.65 as well, where it was tagged (and released
downstream) before being announced.
I read through the Apache Voting process[3] doc, but it doesn't make a
clarification about when the releases should be tagged.
What happens if a vote doesn't pass or get vetoed - do the tags get deleted?
Perhaps the tagging/voting process should include a rc tag instead of a
release tag, so as to avoid getting released downstream accidentally?
Thanks,
Nemo
(Please keep me in cc for replies)
[0]: https://endoflife.date/tomcat
[1]: https://github.com/apache/tomcat,
https://git.apache.org/repos/asf?p=tomcat.git;a=tags
[2]:
https://github.com/endoflife-date/release-data/blob/main/releases/tomcat.json
[3]: https://apache.org/foundation/voting.html#ReleaseVotes
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
