Hi Bruno,
The M name is something Maven uses a lot and (to me) suggests something
users might be more willing to try than anything labeled alpha or beta.
YMMV of course.
>From a compatibility POV, anything can happen until 1.0, so the only name
that matters is 1.0. We have no guidelines except
[+1] Release
Build ok, test ok, site looks ok, reports ok.
Built using:
mvn -version
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /Users/hbiestro/Java/apache-maven-3.8.6
Java version: 1.8.0_352, vendor: Azul Systems, Inc., runtime:
Will try the branch and vote later this week.
>From another thread, I think M1 will behave exatcly like an alpha release
would.
I am more used to alpha/beta/then final release process.
Could you clarify how the M1 will distinguish from an alpha or 1.0 release?
Tha ks for preparing the release!
We have fixed a few bugs and added some enhancements since Apache
Commons IO 2.15.1 was released, so I would like to release Apache
Commons IO 2.16.0.
Apache Commons IO 2.16.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1 (svn
revision 68124)
On Mon, 25 Mar 2024 at 13:12, Gary Gregory wrote:
> Hi All,
>
> 4.5.0 will contain a new package for Bloom Filters.
>
> Since this is a new package and is non-trivial, I propose we release a
> version called 4.5.0-M1 or 4.5.0-beta1 to let users try this out while
> giving us the change to make
We have fixed a few bugs and added some enhancements since Apache
Commons Imaging 1.0-alpha3 was released, so I would like to release
Apache Commons Imaging 1.0.0-M1.
Apache Commons Imaging 1.0.0-M1 RC1 is available for review here:
Hi All,
4.5.0 will contain a new package for Bloom Filters.
Since this is a new package and is non-trivial, I propose we release a
version called 4.5.0-M1 or 4.5.0-beta1 to let users try this out while
giving us the change to make breaking API changes if needed.
Gary
