Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

> > 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. > I see deleted tags ... maybe Maven core repository has another configurations

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

On Sun, Oct 16, 2022 at 8:24 AM Guillaume Nodet wrote: > > Le sam. 15 oct. 2022 à 14:20, Slawomir Jaranowski > 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

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

Le sam. 15 oct. 2022 à 14:20, Slawomir Jaranowski 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,

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

+1 to push manually once the vote suceeded, forks can be used during the vote time. Several asf projects do it with quite some success. Le sam. 15 oct. 2022 à 14:19, Slawomir Jaranowski a écrit : > For failed release I would prefer > - revert commits if needed - we will have history > - remove

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

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

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

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

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

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 a écrit : > Why are you bumping the version if it failed? > > Gary > > On Fri, Oct 14, 2022, 18:13 Guillaume Nodet wrote:

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

Why are you bumping the version if it failed? Gary On Fri, Oct 14, 2022, 18:13 Guillaume Nodet 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

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

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 a écrit : > The master

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

Hello, I agree with Tamás and Maarten. I'm sure I can convince people around me to start using and testing Maven 4 (locally) when it's in alpha, but they would be reluctant if it's a SNAPSHOT. Cheers, Martin Op wo 12 okt. 2022 om 10:01 schreef Tamás Cservenák : > Howdy, > > +1 for release

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

Howdy, +1 for release alpha -1 (not vote but opinion) for snapshots in builds -- but I could live with it T On Wed, Oct 12, 2022 at 9:57 AM Maarten Mulders wrote: > Hi all, > > > TL;DR: +1 for releasing an "4.0.0-alpha-1". > > > I think that an "alpha-1" could also be of value for end users.

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

Hi all, TL;DR: +1 for releasing an "4.0.0-alpha-1". I think that an "alpha-1" could also be of value for end users. They might want to experiment with new features, see if they work on their project. Nowadays, I mostly hear people being reluctant to download a SNAPSHOT from a Jenkins

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

Oh, then isn't it a different game (exposing it for us vs for others)? +1 to enable snapshot, at least for the time we migrate the plugins used in our lifecycles. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

I think the main reason is that the new API isn't stabilized yet. But having it will allow starting migrating some components / plugins to this new API. Actually, I'd be happy with a SNAPSHOT if we were to relax the fact that we don't add snapshot dependencies on master branches. Le mar. 11 oct.

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

Hi Guillaume, Nothing against (even the opposite) but do we have a clear status of what makes it an alpha? A kind of roadmap to final? The rational behind this question is that without it, it will likely look like a SNAPSHOT and will not be tested much but if it is considered alpha cause not well

Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week

I've splitted #819, extracted https://github.com/apache/maven/pull/820 from it and merged that part, so that's fine with me for a first alpha. Le lun. 10 oct. 2022 à 22:32, Guillaume Nodet a écrit : > The master branch contains a lot of things and has not been released for a > long time. With

[DISCUSS] Release Maven 4.0.0-alpha-1 this week

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