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 <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 mar. 11 oct. 2022 à 18:19, Guillaume Nodet <gno...@apache.org> 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 <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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
