Guess for this case a force push is okish since it is pretty sure nobody not able to recover from there would have consumed it. For the future we must not push any tag on apache repo before the release passed - we can use our forks, this way there is no real way to burn any version (this is used by some other ASF projects with success so can be worth a try).
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 ven. 12 janv. 2024 à 12:04, Guillaume Nodet <gno...@apache.org> a écrit : > The explanation in this case, is that the BOM's parent has been changed > yesterday, and I just realized after releasing alpha-11 when looking at the > staging repo, that the groupId was wrong, so I did not call for a vote for > it, fixed the groupId and cut alpha-12. > The other would have been to force push a reset on master and recut > alpha-11. > > Le ven. 12 janv. 2024 à 12:00, Guillaume Nodet <gno...@apache.org> a > écrit : > > > > > > > Le ven. 12 janv. 2024 à 11:47, Romain Manni-Bucau <rmannibu...@gmail.com > > > > a écrit : > > > >> Hi Guillaume, > >> > >> Is it possible to not burn versions, it is always misleading for end > users > >> so would be great to get the alpha 11 out maybe? > >> > > > > It seems it is the rule in the Maven project, but I'd be happy to change > > it. I fully agree. > > > > > >> > >> 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 ven. 12 janv. 2024 à 11:44, Guillaume Nodet <gno...@apache.org> a > >> écrit : > >> > >> > I'm starting a new vote to release this new alpha. > >> > This release brings the latest Maven Resolver 2.0.0-alpha-6, > leveraging > >> > artifact collection filtering and the new transitive dependency > manager. > >> > JLine has been leveraged to provide better line editing, SLF4j has > been > >> > upgraded to 2.x. Also, projects are not resolved anymore outside the > >> > reactor to provide better consistency during builds. > >> > > >> > Fwiw, a few plugins have already been ported to the new API (clean, > >> > install, deploy, resources, compiler) and do pass their integration > >> > tests, i'll update the PR > >> > https://github.com/apache/maven/pull/1048 > >> > <https://github.com/apache/maven/pull/1048/files> asap. > >> > > >> > 13 issues solved: > >> > > >> > > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354059 > >> > > >> > Staging repository: > >> > https://repository.apache.org/content/repositories/maven-2062 > >> > > >> > Dev dist directory: > >> > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-12/ > >> > > >> > Staged site: > >> > https://maven.apache.org/ref/4-LATEST/ > >> > > >> > Guide to testing staged releases: > >> > > http://maven.apache.org/guides/development/guide-testing-releases.html > >> > > >> > Vote open for 72h > >> > > >> > [ ] +1 > >> > [ ] +0 > >> > [ ] -1 > >> > > >> > -- > >> > ------------------------ > >> > Guillaume Nodet > >> > > >> > > > > > > -- > > ------------------------ > > Guillaume Nodet > > > > > > -- > ------------------------ > Guillaume Nodet >
