On Sun, Oct 16, 2022 at 8:24 AM Guillaume Nodet <gno...@apache.org> wrote: > > Le sam. 15 oct. 2022 à 14:20, Slawomir Jaranowski <s.jaranow...@gmail.com> > a écrit : > > > For failed release I would prefer > > - revert commits if needed - we will have history > > - remove tag > > try again :-) > > > > If we bump versions only caused by technical problems during release we > > need to change / create labels in jira, move labeled issues and so on > > And we can have questions why some versions are missing. > > > > > Fully agreed, that's what I initially tried to do. But the repository does > not allow removing a tag. So this would have to be changed.
It does not if your release candidate tag says it's an RC, over at Apache Commons we use, for example, RC tags like "commons-text-1.10.0-RC1", which can be deleted if you want to redo RC1 before you send out the vote. When the vote passes, a new tag on the _same_ commit as the RC commit called "rel/commons-text-1.10.0" is pushed and tags under "rel/" _cannot_ be deleted. Gary > > > > > > > > sob., 15 paź 2022 o 13:31 Benjamin Marwell <bmarw...@apache.org> > > napisał(a): > > > > > Unpopular opinion: > > > Deactivate automatic push. If release:perform went well, push main and > > the > > > tags. > > > > > > Besides, push --delete works for tags, too (if PMC agrees). > > > I doubt there are already forks from the tag active anywhere. > > > But yes, bumping the version is what we used to do in this case. > > > > > > - Ben > > > > > > > > > Am Sa., 15. Okt. 2022 um 00:31 Uhr schrieb Guillaume Nodet < > > > gno...@apache.org>: > > > > > > > > The release:prepare has succeeded but the release:perform failed. > > > > Hence, the tag has been created on github and can't be deleted. > > > > > > > > Le sam. 15 oct. 2022 à 00:26, Gary Gregory <garydgreg...@gmail.com> a > > > > écrit : > > > > > > > > > Why are you bumping the version if it failed? > > > > > > > > > > Gary > > > > > > > > > > On Fri, Oct 14, 2022, 18:13 Guillaume Nodet <gno...@apache.org> > > wrote: > > > > > > > > > > > Just FYI, I've attempted to release 4.0.0-alpha-1, but it failed. > > > I'll > > > > > try > > > > > > to cut another version once the problems are resolved. So > > > 4.0.0-alpha-1 > > > > > is > > > > > > a burnt version and next attempt will be 4.0.0-alpha-2. Stay > > tuned ! > > > > > > > > > > > > Le lun. 10 oct. 2022 à 22:32, Guillaume Nodet <gno...@apache.org> > > a > > > > > écrit > > > > > > : > > > > > > > > > > > > > The master branch contains a lot of things and has not been > > > released > > > > > for > > > > > > a > > > > > > > long time. With the new addition of the v4 api, I think it would > > be > > > > > good > > > > > > to > > > > > > > get something out of the door to gather some feedback from users > > > and > > > > > also > > > > > > > allow migrating some components and plugins to the new API. > > > > > > > > > > > > > > So unless there's an objection, I'd like to start a release > > process > > > > > later > > > > > > > this week after [1] and [2] are merged. > > > > > > > > > > > > > > Thoughts ? > > > > > > > > > > > > > > Cheers, > > > > > > > Guillaume Nodet > > > > > > > > > > > > > > [1] https://github.com/apache/maven/pull/806 > > > > > > > [2] https://github.com/apache/maven/pull/819 > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > ------------------------ > > > > > > Guillaume Nodet > > > > > > > > > > > > > > > > > > > > > > > -- > > > > ------------------------ > > > > Guillaume Nodet > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > -- > > Sławomir Jaranowski > > > > > -- > ------------------------ > Guillaume Nodet --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
