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

2022-10-16 Thread Slawomir Jaranowski 
>
> 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
https://lists.apache.org/list?comm...@maven.apache.org:lte=1y:annotated%20tag%20deleted

I think it is to check - and we should update procedure of release for such
case

-- 
Sławomir Jaranowski

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

2022-10-16 Thread Gary Gregory 
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 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 
> > 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  a
> > > > écrit :
> > > >
> > > > > 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 will be 4.0.0-alpha-2.  Stay
> > tuned !
> > > > > >
> > > > > > 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 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

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

2022-10-16 Thread Guillaume Nodet 
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, 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.


>
>
> sob., 15 paź 2022 o 13:31 Benjamin Marwell 
> 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  a
> > > écrit :
> > >
> > > > 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 will be 4.0.0-alpha-2.  Stay
> tuned !
> > > > >
> > > > > 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 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

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

2022-10-15 Thread Romain Manni-Bucau 
+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 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.
>
>
>
> sob., 15 paź 2022 o 13:31 Benjamin Marwell 
> 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  a
> > > écrit :
> > >
> > > > 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 will be 4.0.0-alpha-2.  Stay
> tuned !
> > > > >
> > > > > 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 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
>

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

2022-10-15 Thread Slawomir Jaranowski 
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.



sob., 15 paź 2022 o 13:31 Benjamin Marwell  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  a
> > écrit :
> >
> > > 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 will be 4.0.0-alpha-2.  Stay tuned !
> > > >
> > > > 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 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

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

2022-10-15 Thread Benjamin Marwell 
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 :
>
> 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:
> >
> > > 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 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

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

2022-10-14 Thread Guillaume Nodet 
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:
>
> > 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 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

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

2022-10-14 Thread Gary Gregory 
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 will be 4.0.0-alpha-2.  Stay tuned !
>
> 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 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
>

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

2022-10-14 Thread Guillaume Nodet 
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 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

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

2022-10-14 Thread Martin Kanters 
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 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. 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 machine. Offering an "alpha-1" - of course, with all the
> > smallprint saying it may ruin your coffee and what not - will give them
> > something to test. And if they test, they can report bugs, so we can
> > stabilise Maven further.
> >
> > We know, they know, it's not stable, things may break - but it's better
> > than postponing Maven 4 and only saying "we will release it when it's
> > ready". Because if nobody tests it in the wild, how do we know it's
> ready?
> >
> >
> > Cheers,
> >
> > Maarten
> >
> > On 11/10/2022 20:13, Romain Manni-Bucau wrote:
> > > 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 tested but "final" in the spirit it will get more
> traction
> > > IMHO.
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Old Blog
> > >  | Github <
> > https://github.com/rmannibucau> |
> > > LinkedIn  | Book
> > > <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> > >
> > >
> > > Le mar. 11 oct. 2022 à 18:19, Guillaume Nodet  a
> > écrit :
> > >
> > >> 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 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
> > >>
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

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

2022-10-12 Thread Tamás Cservenák 
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. 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 machine. Offering an "alpha-1" - of course, with all the
> smallprint saying it may ruin your coffee and what not - will give them
> something to test. And if they test, they can report bugs, so we can
> stabilise Maven further.
>
> We know, they know, it's not stable, things may break - but it's better
> than postponing Maven 4 and only saying "we will release it when it's
> ready". Because if nobody tests it in the wild, how do we know it's ready?
>
>
> Cheers,
>
> Maarten
>
> On 11/10/2022 20:13, Romain Manni-Bucau wrote:
> > 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 tested but "final" in the spirit it will get more traction
> > IMHO.
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> https://github.com/rmannibucau> |
> > LinkedIn  | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> >
> >
> > Le mar. 11 oct. 2022 à 18:19, Guillaume Nodet  a
> écrit :
> >
> >> 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 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
> >>
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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

2022-10-12 Thread Maarten Mulders 

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 machine. Offering an "alpha-1" - of course, with all the 
smallprint saying it may ruin your coffee and what not - will give them 
something to test. And if they test, they can report bugs, so we can 
stabilise Maven further.


We know, they know, it's not stable, things may break - but it's better 
than postponing Maven 4 and only saying "we will release it when it's 
ready". Because if nobody tests it in the wild, how do we know it's ready?



Cheers,

Maarten

On 11/10/2022 20:13, Romain Manni-Bucau wrote:

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 tested but "final" in the spirit it will get more traction
IMHO.

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mar. 11 oct. 2022 à 18:19, Guillaume Nodet  a écrit :


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 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





-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

2022-10-12 Thread Romain Manni-Bucau 
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
 | Github  |
LinkedIn  | Book



Le mer. 12 oct. 2022 à 08:30, Guillaume Nodet  a écrit :

> 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. 2022 à 20:13, Romain Manni-Bucau  a
> écrit :
>
> > 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 tested but "final" in the spirit it will get more traction
> > IMHO.
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn  | Book
> > <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> >
> >
> > Le mar. 11 oct. 2022 à 18:19, Guillaume Nodet  a
> écrit
> > :
> >
> > > 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 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
>

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

2022-10-12 Thread Guillaume Nodet 
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. 2022 à 20:13, Romain Manni-Bucau  a
écrit :

> 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 tested but "final" in the spirit it will get more traction
> IMHO.
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le mar. 11 oct. 2022 à 18:19, Guillaume Nodet  a écrit
> :
>
> > 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 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

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

2022-10-11 Thread Romain Manni-Bucau 
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 tested but "final" in the spirit it will get more traction
IMHO.

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mar. 11 oct. 2022 à 18:19, Guillaume Nodet  a écrit :

> 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 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
>

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

2022-10-11 Thread Guillaume Nodet 
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 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

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

2022-10-10 Thread Guillaume Nodet 
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