For me we have the current "catch up" process == delete and rerun, nobody will have pulled it in a blocking fashion anyway and worse case it is flagged as beta/alpha so not as impacting as finals which are consumed from sources very quickly. Long term process is likely to push the tag on a personal (pmc) github fork and only after the vote push it upstream to be able to drop it without any impact for rerolls.
+1 for this one (no regression on tested projects) but hope it is the last "burn" Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mer. 22 mai 2024 à 21:07, Guillaume Nodet <gno...@apache.org> a écrit : > The main (only ?) reason is that I always forget to create a branch before > releasing. > So master contains beta-2. Or should I rewrite history and force push ? Or > we’d end up with two commits for beta-1 (but a single tag obviously). > If we agree on a mechanism, we should update the release process > accordingly, as I’m blindly following it (hence I forget to create a > branch). > > Guillaume > > > Le mer. 22 mai 2024 à 20:32, Romain Manni-Bucau <rmannibu...@gmail.com> a > écrit : > > > Hi Guillaume, > > > > Why isnt it beta1 - I know but we shouldn't burn version even in > > alpha/beta, every time it makes noise we can't justify technically :(? > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://rmannibucau.metawerx.net/> | Old Blog > > <http://rmannibucau.wordpress.com> | Github < > > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > > < > > > https://www.packtpub.com/application-development/java-ee-8-high-performance > > > > > > > > > Le mer. 22 mai 2024 à 17:12, Guillaume Nodet <gno...@apache.org> a > écrit : > > > > > This is a vote to release Apache Maven 4.0.0-beta-3, as I've cut > another > > > release to fix blocking issues found in beta-2. > > > > > > > > > We solved 25 issues: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354634 > > > > > > There are still some issues in JIRA: > > > https://issues.apache.org/jira/projects/MNG/issues > > > > > > Release candidates: > > > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-beta-3/ > > > > > > Staging repository: > > > https://repository.apache.org/content/repositories/maven-2126/ > > > > > > Source release SHA512: > > > - apache-maven-4.0.0-beta-3-src.zip > > > > > > > > > 4125acba32218e341b34c1bbe7700f5aa71947fd1a6a5d418825822099800e3b798a5300eaf711e0709866b7e5fc6fee323515af18d8ab25d7eaac034d72b1c6 > > > - apache-maven-4.0.0-beta-3-src.tar.gz > > > > > > > > > 8ca063a72fdacbcbe4afc33fc46e6c8920327092d11f3d8a77723ce995c3e24d1e8413cce3d5bc59a47657316834bfb9d4706d8bdffa5da5e147bcb404381808 > > > > > > Staging site: > > > https://maven.apache.org/ref/4-LATEST/ > > > > > > Guide to testing staged releases: > > > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > > > The vote is open for at least 72 hours. > > > > > > [ ] +1 > > > [ ] +0 > > > [ ] -1 > > > > > > -------------- > > > Guillaume Nodet > > > > > >
