Re: [VOTE] Release Apache Maven version 3.8.0

[Robert Scholte]

Giving dev extra expression is the most important improvement. This is what I 
missed.

To have everything in chronological order, I would like to move this paragraph 
after 

"To produce a release candidate, follow the first seven steps only from the 
following procedure:
Maven Project Common Release Procedure"


Also, 'first seven steps' should be replaced with 'up to and including Stage 
The Release', so you don't have to count and it won't matter if there steps 
added or removed.

And to be complete I think we should add: Adjust the URLs of the staging repos 
of the Call for Vote template.

Robert
On 27-3-2021 07:46:14, Arnaud Héritier  wrote:
+1

On Sat, Mar 27, 2021 at 4:03 AM Mark Derricutt wrote:

> Mostly reads good to me, only minor niggle to me is:
>
> Then once the vote passed, svn move to release
>
> which I think might be grammatically better:
>
> “Once the vote has passed, svn move to the release tree ”
>
> +1.5 non-binding :)
>
>
>
>
> From: Hervé BOUTEMY
> Reply: Maven Developers List
> Date: 27 March 2021 at 2:19:48 PM
> To: Maven Developers List
> Subject: Re: [VOTE] Release Apache Maven version 3.8.0
>
> first pass of documentation improvement done in
>
> github.com/apache/maven-site/commit/ec73b445adc7012e1384cf1b89af3f0a6f5eee17
> please all review and see if anything you read may be mis-interpreted when
> reading fast
>


--
Arnaud Héritier
Twitter/Skype : aheritier

Re: [VOTE] Release Apache Maven version 3.8.0

[Arnaud Héritier]

+1

On Sat, Mar 27, 2021 at 4:03 AM Mark Derricutt  wrote:

> Mostly reads good to me, only minor niggle to me is:
>
> Then once the vote passed, svn move to release
>
> which I think might be grammatically better:
>
> “Once the vote has passed, svn move to the release tree ”
>
> +1.5 non-binding :)
>
>
>
>
> From: Hervé BOUTEMY  
> Reply: Maven Developers List  
> Date: 27 March 2021 at 2:19:48 PM
> To: Maven Developers List  
> Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
>
> first pass of documentation improvement done in
>
> github.com/apache/maven-site/commit/ec73b445adc7012e1384cf1b89af3f0a6f5eee17
> please all review and see if anything you read may be mis-interpreted when
> reading fast
>


-- 
Arnaud Héritier
Twitter/Skype : aheritier

Re: [VOTE] Release Apache Maven version 3.8.0

[Mark Derricutt]

Mostly reads good to me, only minor niggle to me is:

Then once the vote passed, svn move to release

which I think might be grammatically better:

“Once the vote has passed, svn move to the release tree ”

+1.5 non-binding :)




From: Hervé BOUTEMY  
Reply: Maven Developers List  
Date: 27 March 2021 at 2:19:48 PM
To: Maven Developers List  
Subject:  Re: [VOTE] Release Apache Maven version 3.8.0

first pass of documentation improvement done in
github.com/apache/maven-site/commit/ec73b445adc7012e1384cf1b89af3f0a6f5eee17
please all review and see if anything you read may be mis-interpreted when
reading fast

Re: [VOTE] Release Apache Maven version 3.8.0

[Hervé BOUTEMY]

first pass of documentation improvement done  in
https://github.com/apache/maven-site/commit/ec73b445adc7012e1384cf1b89af3f0a6f5eee17

please all review and see if anything you read may be mis-interpreted when 
reading fast

I don't know if providing a script to create a staging tree (with binaries + 
source, which is another topic that in the past was failed at copy/pasting) 
would help
or simply a template svn subtree to copy to init a staging...
we need something simple, that is obvious to work with (and not a new tedious 
additional tool)

Regards,

Hervé

Le vendredi 26 mars 2021, 10:44:41 CET Robert Scholte a écrit :
> Looks like I misinterpreted the instructions of maven-core-release[1]
> Will rewrite it to prevent this the next time.
> 
> sorry about that,
> Robert
> 
> [1] https://maven.apache.org/developers/release/maven-core-release.html
> 
> On 26-3-2021 09:45:59, Olivier Lamy  wrote:
> Fixed this has been removed from archive area
> 
> On Fri, 26 Mar 2021 at 5:29 pm, Maxim Solodovnik
> 
> wrote:
> > On Fri, 26 Mar 2021 at 14:24, Guillaume Nodet wrote:
> > > And that's expected as archive.apache.org keeps all releases that are
> > 
> > not
> > 
> > > current, i.e. those that have been removed from dist.apache.org.
> > 
> > Actually release is added to the archive as soon as the release is
> > uploaded (not removed :)
> > 
> > > The release process should really be fixed and the commit to
> > 
> > dist.apache.org
> > 
> > > should really happen after the vote.
> > > I suggest sending an email to infra to see if the binaries can be
> > > removed
> > > from archive.apache.org.
> > > 
> > > In any case, I'm -0 on this release. I'm also concerned about the leap
> > 
> > in
> > 
> > > the release numbering. You need to balance how many people will wonder
> > 
> > why
> > 
> > > 3.7.0 can not be found vs the number of people who were expecting a
> > 
> > feature
> > 
> > > in 3.7.0 (which they would expect to be in 3.8.0 anyway). A failed
> > 
> > attempt
> > 
> > > should not lead to a missing release number either, as the failure stays
> > 
> > in
> > 
> > > the dev community, so I don't think the larger user audience cares about
> > > those...
> > > 
> > > 
> > > 
> > > Le ven. 26 mars 2021 à 08:17, Maxim Solodovnik a
> > > 
> > > écrit :
> > > > Hello,
> > > > 
> > > > Moving might not do what is expected
> > > > the binaries are already in
> > > > http://archive.apache.org/dist/maven/maven-3/3.8.0/
> > > > 
> > > > On Fri, 26 Mar 2021 at 11:25, Olivier Lamy wrote:
> > > > > Yes you're right that shouldn't be there as this has been mirrored
> > 
> > in all
> > 
> > > > > Apache mirrors as a real release...
> > > > > 
> > > > > The procedure
> > > > > http://maven.apache.org/developers/release/maven-core-release.html
> > 
> > says:
> > > > > "
> > > > > 
> > > > > For non-alpha/beta releases, release candidates are produced before
> > 
> > the
> > 
> > > > > actual release.
> > > > > 
> > > > > Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then
> > > > 
> > > > create
> > > > 
> > > > > the necessary directory tree.
> > > > > 
> > > > > "
> > > > > 
> > > > > @Robert I moved the binaries. As the vote is not finished they
> > 
> > shouldn;t
> > 
> > > > be
> > > > 
> > > > > in the official Apache release download area
> > > > > 
> > > > > svn mv
> > 
> > https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
> > 
> > > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/
> > > > > 
> > > > > Committing transaction...
> > > > > 
> > > > > Committed revision 46741.
> > > > > 
> > > > > On Fri, 26 Mar 2021 at 13:18, Mark Derricutt
> > 
> > wrote:
> > > > > > I notice in the vote email we have mentioned:
> > dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-mav
> > en–3.8.0-bin.zip> 
> > > > <
> > 
> > http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/bina

[CANCELLED] [VOTE] Release Apache Maven version 3.8.0

[Robert Scholte]

Based on the finding by Maarten I'll drop the release.
We'll work on a new one.

thanks,
Robert

On 22-3-2021 20:40:41, Robert Scholte  wrote:
Hi,

For the details about this release, please read 
https://maven.apache.org/docs/3.8.0/release-notes.html
Also please provide feedback on the release notes. (as you know, these are 
published separately from the release, so it doesn't have to block the release 
itself)

We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1633/

https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip


Source release checksum(s):
apache-maven-3.8.0-bin.zip sha512: 
b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
apache-maven-3.8.0-src.zip sha512: 
51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893


Staging site:
https://maven.apache.org/ref/3-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

Re: [VOTE] Release Apache Maven version 3.8.0

[Robert Scholte]

Looks like I misinterpreted the instructions of maven-core-release[1]
Will rewrite it to prevent this the next time.

sorry about that,
Robert

[1] https://maven.apache.org/developers/release/maven-core-release.html

On 26-3-2021 09:45:59, Olivier Lamy  wrote:
Fixed this has been removed from archive area

On Fri, 26 Mar 2021 at 5:29 pm, Maxim Solodovnik
wrote:

> On Fri, 26 Mar 2021 at 14:24, Guillaume Nodet wrote:
> >
> > And that's expected as archive.apache.org keeps all releases that are
> not
> > current, i.e. those that have been removed from dist.apache.org.
>
> Actually release is added to the archive as soon as the release is
> uploaded (not removed :)
>
> > The release process should really be fixed and the commit to
> dist.apache.org
> > should really happen after the vote.
> > I suggest sending an email to infra to see if the binaries can be removed
> > from archive.apache.org.
> >
> > In any case, I'm -0 on this release. I'm also concerned about the leap
> in
> > the release numbering. You need to balance how many people will wonder
> why
> > 3.7.0 can not be found vs the number of people who were expecting a
> feature
> > in 3.7.0 (which they would expect to be in 3.8.0 anyway). A failed
> attempt
> > should not lead to a missing release number either, as the failure stays
> in
> > the dev community, so I don't think the larger user audience cares about
> > those...
> >
> >
> >
> > Le ven. 26 mars 2021 à 08:17, Maxim Solodovnik a
> > écrit :
> >
> > > Hello,
> > >
> > > Moving might not do what is expected
> > > the binaries are already in
> > > http://archive.apache.org/dist/maven/maven-3/3.8.0/
> > >
> > > On Fri, 26 Mar 2021 at 11:25, Olivier Lamy wrote:
> > > >
> > > > Yes you're right that shouldn't be there as this has been mirrored
> in all
> > > > Apache mirrors as a real release...
> > > >
> > > > The procedure
> > > > http://maven.apache.org/developers/release/maven-core-release.html
> says:
> > > > "
> > > >
> > > > For non-alpha/beta releases, release candidates are produced before
> the
> > > > actual release.
> > > >
> > > > Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then
> > > create
> > > > the necessary directory tree.
> > > >
> > > > "
> > > >
> > > > @Robert I moved the binaries. As the vote is not finished they
> shouldn;t
> > > be
> > > > in the official Apache release download area
> > > >
> > > > svn mv
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
> > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/
> > > >
> > > > Committing transaction...
> > > >
> > > > Committed revision 46741.
> > > >
> > > > On Fri, 26 Mar 2021 at 13:18, Mark Derricutt
> wrote:
> > > >
> > > > > I notice in the vote email we have mentioned:
> > > > >
> > > > >
> > > > >
> > >
> dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
>
> > > <
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> >
> > > > > <
> > >
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > > >
> > > > > <
> > > > >
> > >
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > > > > >
> > > > >
> > > > > which doesn’t really highlight anywhere that this is a
> > > staging/unreleased
> > > > > version.
> > > > >
> > > > > Tho changing that probably won’t change too much here.
> > > > >
> > > > > *ponders*
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: Gary Gregory <
> garydgreg...@gmail.com>
> > > > > Reply: Maven Developers List <
> > > dev@maven.apache.org>
> > > > > Date: 26 March 2021 at 2:13:05 PM
> > > > > To: Maven Developers List <
> dev@maven.apache.org
> > > >
> > > > > Subject: Re: [VOTE] Release Apache Maven version 3.8.0
> > > > >
> > > > > It's pretty clear to me that the Maven release process is broken
> when
> > > > > people are getting new versions they think are real and valid when
> in
> > > fact
> > > > > it is a release candidate vote in in progress. Gary
> > > > >
> > > >
> > > >
> > > > --
> > > > Olivier Lamy
> > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Maxim
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
> > --
> > 
> > Guillaume Nodet
>
>
>
> --
> Best regards,
> Maxim
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Release Apache Maven version 3.8.0

[Olivier Lamy]

Fixed this has been removed from archive area

On Fri, 26 Mar 2021 at 5:29 pm, Maxim Solodovnik 
wrote:

> On Fri, 26 Mar 2021 at 14:24, Guillaume Nodet  wrote:
> >
> > And that's expected as archive.apache.org keeps all releases that are
> not
> > current, i.e. those that have been removed from dist.apache.org.
>
> Actually release is added to the archive as soon as the release is
> uploaded (not removed :)
>
> > The release process should really be fixed and the commit to
> dist.apache.org
> > should really happen after the vote.
> > I suggest sending an email to infra to see if the binaries can be removed
> > from archive.apache.org.
> >
> > In any case, I'm -0 on this release.  I'm also concerned about the leap
> in
> > the release numbering.  You need to balance how many people will wonder
> why
> > 3.7.0 can not be found vs the number of people who were expecting a
> feature
> > in 3.7.0 (which they would expect to be in 3.8.0 anyway).  A failed
> attempt
> > should not lead to a missing release number either, as the failure stays
> in
> > the dev community, so I don't think the larger user audience cares about
> > those...
> >
> >
> >
> > Le ven. 26 mars 2021 à 08:17, Maxim Solodovnik  a
> > écrit :
> >
> > > Hello,
> > >
> > > Moving might not do what is expected
> > > the binaries are already in
> > > http://archive.apache.org/dist/maven/maven-3/3.8.0/
> > >
> > > On Fri, 26 Mar 2021 at 11:25, Olivier Lamy  wrote:
> > > >
> > > > Yes you're right that shouldn't be there as this has been mirrored
> in all
> > > > Apache mirrors as a real release...
> > > >
> > > > The procedure
> > > > http://maven.apache.org/developers/release/maven-core-release.html
> says:
> > > > "
> > > >
> > > > For non-alpha/beta releases, release candidates are produced before
> the
> > > > actual release.
> > > >
> > > > Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then
> > > create
> > > > the necessary directory tree.
> > > >
> > > > "
> > > >
> > > > @Robert I moved the binaries. As the vote is not finished they
> shouldn;t
> > > be
> > > > in the official Apache release download area
> > > >
> > > > svn mv
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
> > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/
> > > >
> > > > Committing transaction...
> > > >
> > > > Committed revision 46741.
> > > >
> > > > On Fri, 26 Mar 2021 at 13:18, Mark Derricutt 
> wrote:
> > > >
> > > > > I notice in the vote email we have mentioned:
> > > > >
> > > > >
> > > > >
> > >
> dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
> <http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip>
> > > <
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> >
> > > > > <
> > >
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > > >
> > > > > <
> > > > >
> > >
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > > > > >
> > > > >
> > > > > which doesn’t really highlight anywhere that this is a
> > > staging/unreleased
> > > > > version.
> > > > >
> > > > > Tho changing that probably won’t change too much here.
> > > > >
> > > > > *ponders*
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: Gary Gregory  <
> garydgreg...@gmail.com>
> > > > > Reply: Maven Developers List  <
> > > dev@maven.apache.org>
> > > > > Date: 26 March 2021 at 2:13:05 PM
> > > > > To: Maven Developers List  <
> dev@maven.apache.org
> > > >
> > > > > Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
> > > > >
> > > > > It's pretty clear to me that the Maven release process is broken
> when
> > > > > people are getting new versions they think are real and valid when
> in
> > > fact
> > > > > it is a release candidate vote in in progress. Gary
> > > > >
> > > >
> > > >
> > > > --
> > > > Olivier Lamy
> > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Maxim
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
> > --
> > 
> > Guillaume Nodet
>
>
>
> --
> Best regards,
> Maxim
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Release Apache Maven version 3.8.0

[Maxim Solodovnik]

On Fri, 26 Mar 2021 at 14:24, Guillaume Nodet  wrote:
>
> And that's expected as archive.apache.org keeps all releases that are not
> current, i.e. those that have been removed from dist.apache.org.

Actually release is added to the archive as soon as the release is
uploaded (not removed :)

> The release process should really be fixed and the commit to dist.apache.org
> should really happen after the vote.
> I suggest sending an email to infra to see if the binaries can be removed
> from archive.apache.org.
>
> In any case, I'm -0 on this release.  I'm also concerned about the leap in
> the release numbering.  You need to balance how many people will wonder why
> 3.7.0 can not be found vs the number of people who were expecting a feature
> in 3.7.0 (which they would expect to be in 3.8.0 anyway).  A failed attempt
> should not lead to a missing release number either, as the failure stays in
> the dev community, so I don't think the larger user audience cares about
> those...
>
>
>
> Le ven. 26 mars 2021 à 08:17, Maxim Solodovnik  a
> écrit :
>
> > Hello,
> >
> > Moving might not do what is expected
> > the binaries are already in
> > http://archive.apache.org/dist/maven/maven-3/3.8.0/
> >
> > On Fri, 26 Mar 2021 at 11:25, Olivier Lamy  wrote:
> > >
> > > Yes you're right that shouldn't be there as this has been mirrored in all
> > > Apache mirrors as a real release...
> > >
> > > The procedure
> > > http://maven.apache.org/developers/release/maven-core-release.html says:
> > > "
> > >
> > > For non-alpha/beta releases, release candidates are produced before the
> > > actual release.
> > >
> > > Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then
> > create
> > > the necessary directory tree.
> > >
> > > "
> > >
> > > @Robert I moved the binaries. As the vote is not finished they shouldn;t
> > be
> > > in the official Apache release download area
> > >
> > > svn mv https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
> > > https://dist.apache.org/repos/dist/dev/maven/maven-3/
> > >
> > > Committing transaction...
> > >
> > > Committed revision 46741.
> > >
> > > On Fri, 26 Mar 2021 at 13:18, Mark Derricutt  wrote:
> > >
> > > > I notice in the vote email we have mentioned:
> > > >
> > > >
> > > >
> > dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
> > <http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip>
> > > > <
> > http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > >
> > > > <
> > > >
> > http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > > > >
> > > >
> > > > which doesn’t really highlight anywhere that this is a
> > staging/unreleased
> > > > version.
> > > >
> > > > Tho changing that probably won’t change too much here.
> > > >
> > > > *ponders*
> > > >
> > > >
> > > >
> > > >
> > > > From: Gary Gregory  
> > > > Reply: Maven Developers List  <
> > dev@maven.apache.org>
> > > > Date: 26 March 2021 at 2:13:05 PM
> > > > To: Maven Developers List   > >
> > > > Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
> > > >
> > > > It's pretty clear to me that the Maven release process is broken when
> > > > people are getting new versions they think are real and valid when in
> > fact
> > > > it is a release candidate vote in in progress. Gary
> > > >
> > >
> > >
> > > --
> > > Olivier Lamy
> > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
> >
> >
> > --
> > Best regards,
> > Maxim
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> --
> 
> Guillaume Nodet



-- 
Best regards,
Maxim

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

Re: [VOTE] Release Apache Maven version 3.8.0

[Guillaume Nodet]

And that's expected as archive.apache.org keeps all releases that are not
current, i.e. those that have been removed from dist.apache.org.
The release process should really be fixed and the commit to dist.apache.org
should really happen after the vote.
I suggest sending an email to infra to see if the binaries can be removed
from archive.apache.org.

In any case, I'm -0 on this release.  I'm also concerned about the leap in
the release numbering.  You need to balance how many people will wonder why
3.7.0 can not be found vs the number of people who were expecting a feature
in 3.7.0 (which they would expect to be in 3.8.0 anyway).  A failed attempt
should not lead to a missing release number either, as the failure stays in
the dev community, so I don't think the larger user audience cares about
those...



Le ven. 26 mars 2021 à 08:17, Maxim Solodovnik  a
écrit :

> Hello,
>
> Moving might not do what is expected
> the binaries are already in
> http://archive.apache.org/dist/maven/maven-3/3.8.0/
>
> On Fri, 26 Mar 2021 at 11:25, Olivier Lamy  wrote:
> >
> > Yes you're right that shouldn't be there as this has been mirrored in all
> > Apache mirrors as a real release...
> >
> > The procedure
> > http://maven.apache.org/developers/release/maven-core-release.html says:
> > "
> >
> > For non-alpha/beta releases, release candidates are produced before the
> > actual release.
> >
> > Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then
> create
> > the necessary directory tree.
> >
> > "
> >
> > @Robert I moved the binaries. As the vote is not finished they shouldn;t
> be
> > in the official Apache release download area
> >
> > svn mv https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
> > https://dist.apache.org/repos/dist/dev/maven/maven-3/
> >
> > Committing transaction...
> >
> > Committed revision 46741.
> >
> > On Fri, 26 Mar 2021 at 13:18, Mark Derricutt  wrote:
> >
> > > I notice in the vote email we have mentioned:
> > >
> > >
> > >
> dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
> <http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip>
> > > <
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> >
> > > <
> > >
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > > >
> > >
> > > which doesn’t really highlight anywhere that this is a
> staging/unreleased
> > > version.
> > >
> > > Tho changing that probably won’t change too much here.
> > >
> > > *ponders*
> > >
> > >
> > >
> > >
> > > From: Gary Gregory  
> > > Reply: Maven Developers List  <
> dev@maven.apache.org>
> > > Date: 26 March 2021 at 2:13:05 PM
> > > To: Maven Developers List   >
> > > Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
> > >
> > > It's pretty clear to me that the Maven release process is broken when
> > > people are getting new versions they think are real and valid when in
> fact
> > > it is a release candidate vote in in progress. Gary
> > >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Best regards,
> Maxim
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven version 3.8.0

[Olivier Lamy]

ouchhh I will check with infra. if they can delete this :(


On Fri, 26 Mar 2021 at 17:17, Maxim Solodovnik  wrote:

> Hello,
>
> Moving might not do what is expected
> the binaries are already in
> http://archive.apache.org/dist/maven/maven-3/3.8.0/
>
> On Fri, 26 Mar 2021 at 11:25, Olivier Lamy  wrote:
> >
> > Yes you're right that shouldn't be there as this has been mirrored in all
> > Apache mirrors as a real release...
> >
> > The procedure
> > http://maven.apache.org/developers/release/maven-core-release.html says:
> > "
> >
> > For non-alpha/beta releases, release candidates are produced before the
> > actual release.
> >
> > Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then
> create
> > the necessary directory tree.
> >
> > "
> >
> > @Robert I moved the binaries. As the vote is not finished they shouldn;t
> be
> > in the official Apache release download area
> >
> > svn mv https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
> > https://dist.apache.org/repos/dist/dev/maven/maven-3/
> >
> > Committing transaction...
> >
> > Committed revision 46741.
> >
> > On Fri, 26 Mar 2021 at 13:18, Mark Derricutt  wrote:
> >
> > > I notice in the vote email we have mentioned:
> > >
> > >
> > >
> dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
> <http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip>
> > > <
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> >
> > > <
> > >
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > > >
> > >
> > > which doesn’t really highlight anywhere that this is a
> staging/unreleased
> > > version.
> > >
> > > Tho changing that probably won’t change too much here.
> > >
> > > *ponders*
> > >
> > >
> > >
> > >
> > > From: Gary Gregory  
> > > Reply: Maven Developers List  <
> dev@maven.apache.org>
> > > Date: 26 March 2021 at 2:13:05 PM
> > > To: Maven Developers List   >
> > > Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
> > >
> > > It's pretty clear to me that the Maven release process is broken when
> > > people are getting new versions they think are real and valid when in
> fact
> > > it is a release candidate vote in in progress. Gary
> > >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Best regards,
> Maxim
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Release Apache Maven version 3.8.0

[Enrico Olivelli]

The problem is that Robert uploaded the binaries to the "dist/release" directory

this is to be done only after the vote completes

IIRC we have dist/dev for staging releasing

Enrico

Il giorno ven 26 mar 2021 alle ore 08:17 Maxim Solodovnik
 ha scritto:
>
> Hello,
>
> Moving might not do what is expected
> the binaries are already in 
> http://archive.apache.org/dist/maven/maven-3/3.8.0/
>
> On Fri, 26 Mar 2021 at 11:25, Olivier Lamy  wrote:
> >
> > Yes you're right that shouldn't be there as this has been mirrored in all
> > Apache mirrors as a real release...
> >
> > The procedure
> > http://maven.apache.org/developers/release/maven-core-release.html says:
> > "
> >
> > For non-alpha/beta releases, release candidates are produced before the
> > actual release.
> >
> > Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then create
> > the necessary directory tree.
> >
> > "
> >
> > @Robert I moved the binaries. As the vote is not finished they shouldn;t be
> > in the official Apache release download area
> >
> > svn mv https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
> > https://dist.apache.org/repos/dist/dev/maven/maven-3/
> >
> > Committing transaction...
> >
> > Committed revision 46741.
> >
> > On Fri, 26 Mar 2021 at 13:18, Mark Derricutt  wrote:
> >
> > > I notice in the vote email we have mentioned:
> > >
> > >
> > > dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
> > > <http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip>
> > > <
> > > http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > > >
> > >
> > > which doesn’t really highlight anywhere that this is a staging/unreleased
> > > version.
> > >
> > > Tho changing that probably won’t change too much here.
> > >
> > > *ponders*
> > >
> > >
> > >
> > >
> > > From: Gary Gregory  
> > > Reply: Maven Developers List  
> > > Date: 26 March 2021 at 2:13:05 PM
> > > To: Maven Developers List  
> > > Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
> > >
> > > It's pretty clear to me that the Maven release process is broken when
> > > people are getting new versions they think are real and valid when in fact
> > > it is a release candidate vote in in progress. Gary
> > >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Best regards,
> Maxim
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

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

Re: [VOTE] Release Apache Maven version 3.8.0

[Maxim Solodovnik]

Hello,

Moving might not do what is expected
the binaries are already in http://archive.apache.org/dist/maven/maven-3/3.8.0/

On Fri, 26 Mar 2021 at 11:25, Olivier Lamy  wrote:
>
> Yes you're right that shouldn't be there as this has been mirrored in all
> Apache mirrors as a real release...
>
> The procedure
> http://maven.apache.org/developers/release/maven-core-release.html says:
> "
>
> For non-alpha/beta releases, release candidates are produced before the
> actual release.
>
> Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then create
> the necessary directory tree.
>
> "
>
> @Robert I moved the binaries. As the vote is not finished they shouldn;t be
> in the official Apache release download area
>
> svn mv https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
> https://dist.apache.org/repos/dist/dev/maven/maven-3/
>
> Committing transaction...
>
> Committed revision 46741.
>
> On Fri, 26 Mar 2021 at 13:18, Mark Derricutt  wrote:
>
> > I notice in the vote email we have mentioned:
> >
> >
> > dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
> > <http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip>
> > <
> > http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > >
> >
> > which doesn’t really highlight anywhere that this is a staging/unreleased
> > version.
> >
> > Tho changing that probably won’t change too much here.
> >
> > *ponders*
> >
> >
> >
> >
> > From: Gary Gregory  
> > Reply: Maven Developers List  
> > Date: 26 March 2021 at 2:13:05 PM
> > To: Maven Developers List  
> > Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
> >
> > It's pretty clear to me that the Maven release process is broken when
> > people are getting new versions they think are real and valid when in fact
> > it is a release candidate vote in in progress. Gary
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Best regards,
Maxim

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

Re: [VOTE] Release Apache Maven version 3.8.0

[Olivier Lamy]

Yes you're right that shouldn't be there as this has been mirrored in all
Apache mirrors as a real release...

The procedure
http://maven.apache.org/developers/release/maven-core-release.html says:
"

For non-alpha/beta releases, release candidates are produced before the
actual release.

Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then create
the necessary directory tree.

"

@Robert I moved the binaries. As the vote is not finished they shouldn;t be
in the official Apache release download area

svn mv https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
https://dist.apache.org/repos/dist/dev/maven/maven-3/

Committing transaction...

Committed revision 46741.

On Fri, 26 Mar 2021 at 13:18, Mark Derricutt  wrote:

> I notice in the vote email we have mentioned:
>
>
> dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
> <http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip>
> <
> http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> >
>
> which doesn’t really highlight anywhere that this is a staging/unreleased
> version.
>
> Tho changing that probably won’t change too much here.
>
> *ponders*
>
>
>
>
> From: Gary Gregory  
> Reply: Maven Developers List  
> Date: 26 March 2021 at 2:13:05 PM
> To: Maven Developers List  
> Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
>
> It's pretty clear to me that the Maven release process is broken when
> people are getting new versions they think are real and valid when in fact
> it is a release candidate vote in in progress. Gary
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Release Apache Maven version 3.8.0

[Mark Derricutt]

I notice in the vote email we have mentioned:

dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
<http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip>

which doesn’t really highlight anywhere that this is a staging/unreleased
version.

Tho changing that probably won’t change too much here.

*ponders*




From: Gary Gregory  
Reply: Maven Developers List  
Date: 26 March 2021 at 2:13:05 PM
To: Maven Developers List  
Subject:  Re: [VOTE] Release Apache Maven version 3.8.0

It's pretty clear to me that the Maven release process is broken when
people are getting new versions they think are real and valid when in fact
it is a release candidate vote in in progress. Gary

Re: [VOTE] Release Apache Maven version 3.8.0

[Gary Gregory]

It's pretty clear to me that the Maven release process is broken when
people are getting new versions they think are real and valid when in fact
it is a release candidate vote in in progress.

Gary


On Thu, Mar 25, 2021, 19:17 Nick Stolwijk  wrote:

> Also +1 (non-binding) for me. I ran a chocolatey upgrade and I also have
> Maven 3.8.0.
>
> nicks@DESKTOP-HHAT2G9 (voyager) ~
> 00:15:29 $ mvn --version
> Apache Maven 3.8.0 (6aa1f4acf5d6323e9aa08b763cb9933dc96749b9)
> Maven home: C:\ProgramData\chocolatey\lib\maven\apache-maven-3.8.0
> Java version: 16, vendor: Oracle Corporation, runtime: C:\Program
> Files\OpenJDK\jdk-16
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> It seems such installers are (too) quick to upgrade.
>
> With regards,
>
> Nick Stolwijk
>
> ~~~ Try to leave this world a little better than you found it and, when
> your turn comes to die, you can die happy in feeling that at any rate you
> have not wasted your time but have done your best ~~~
>
> Lord Baden-Powell
>
>
> On Fri, Mar 26, 2021 at 12:05 AM Mark Derricutt  wrote:
>
> > +1 non-binding from me, tho I have (potential) concerns.
> >
> > I’d missed seeing the emails about the release vote, but DID notice that
> > Mac Homebrew had upgraded me magically to 3.8.0.
> >
> > Which led me to tweeting that it seemed the download page wasn’t updated
> (
> > then a followup about home-brew jumping the gun):
> >
> > https://twitter.com/talios/status/1374188445380214784
> >
> > Carlo Cabrera responded that he reverted the change in Homebrew:
> >
> > https://twitter.com/carlocab_/status/1374230372112867330
> >
> > tho, anyone who happened to download the update, still has that update
> > installed.
> >
> > Downloading the zip here, and checking:
> >
> > ~/Downloads/Download Sync/apache-maven-3.8.0 ❯ ./bin/mvn -version
> > Apache Maven 3.8.0 (6aa1f4acf5d6323e9aa08b763cb9933dc96749b9)
> > Maven home: /Users/amrk/Downloads/Download Sync/apache-maven-3.8.0
> > Java version: 1.8.0_282, vendor: Azul Systems, Inc., runtime:
> >
> >
> /Users/amrk/.sdkman/candidates/java/8.0.282-zulu/zulu-8.jdk/Contents/Home/jre
> > Default locale: en_NZ, platform encoding: UTF-8
> > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> > ~/Downloads/Download Sync/apache-maven-3.8.0 took 3s ❯ mvn --version
> > Apache Maven 3.8.0 (6aa1f4acf5d6323e9aa08b763cb9933dc96749b9)
> > Maven home: /usr/local/Cellar/maven/3.8.0/libexec
> > Java version: 1.8.0_282, vendor: Azul Systems, Inc., runtime:
> >
> >
> /Users/amrk/.sdkman/candidates/java/8.0.282-zulu/zulu-8.jdk/Contents/Home/jre
> > Default locale: en_NZ, platform encoding: UTF-8
> > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> >
> > both releases have the same SHA1 for the build - so in this instance I’m
> > happy for a +1.
> >
> > Tho I wonder what the recourse would be if needing to respin the release
> -
> > 3.8.1 version bump or?
> >
> > Is there anyway to prevent this happening again? ( Probably off-thread
> > replies would be best ).
> >
> > Mark
> >
> >
> >
> >
> > From: Tibor Digana  
> > Reply: Maven Developers List  <
> dev@maven.apache.org>
> > Date: 26 March 2021 at 8:05:51 AM
> > To: Maven Developers List  
> > Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
> >
> > here is mine +1.
> > The amount of work means more for me than the version 3.7.0 we skipped.
> We
> > can improve it in the future of course!
> > Regarding the issues found with the Warning on the console, these issues
> > can be fixed as always, right after.
> > T
> >
> > On Mon, Mar 22, 2021 at 8:40 PM Robert Scholte 
> > wrote:
> >
> > > Hi,
> > >
> > > For the details about this release, please read
> > > https://maven.apache.org/docs/3.8.0/release-notes.html
> > > Also please provide feedback on the release notes. (as you know, these
> > are
> > > published separately from the release, so it doesn't have to block the
> > > release itself)
> > >
> > > We solved 5 issues:
> > >
> > >
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
> > >
> > > There are still a couple of issues left in JIRA:
> > >
> > >
&

Re: [VOTE] Release Apache Maven version 3.8.0

[Hervé BOUTEMY]

I'm not worried about attempt to download: the issue you found proves that the 
value of the mirror url blocks anything, even if not really the ideal way

but you're right that it's hard to understand from a user perspective...

I just managed to fix the issue:
https://github.com/apache/maven/commit/d295dc362fe7d7b189b4976a5742a17362eb51a1

perhaps we should respin 3.8.1

Regards,

Hervé

Le mercredi 24 mars 2021, 20:51:10 CET Maarten Mulders a écrit :
> A 0-vote from my side. As far as I can tell, non-TLS repos are indeed
> blocked. That is the main reason for cutting this release, and it works,
> which is good.
> 
> But if I understood Hervé correctly, the message that appears when Maven
> attempts download of an artifact over a non-TLS connection differs
> depending on which component attempted the download. This has two
> consequences:
> 
> 1. The message is sometimes pretty clear, but sometimes rather vague. An
> example of the latter one: "Checksum validation failed, expected Lorem
> but is a0a3234b13da255645808f53efb387d26ae441db". One must be quite
> clever to deduce that Maven attempted to download something over HTTP.
> 
> 2. I am worried that we may have missed a component that also attempts
> to download artifacts, and still allows non-HTTP connections.
> 
> 
> Maybe I didn't understand correctly - I actually hope so. In that case,
> please explain me where my understanding is wrong.
> 
> Thanks,
> 
> 
> Maarten
> 
> On March 24th, 2021 at 18:54, Gary Gregory wrote:
> > Whenever I have to explain to colleagues that Maven "burns" version
> > numbers
> > when a release candidate fails or some other obtuse reason, they are just
> > as baffled as I am. In the end it does not matter it's just bizarre.
> > 
> > Gary
> > 
> > On Tue, Mar 23, 2021, 20:58 Olivier Lamy  wrote:
> >> +0
> >> Same reason as Ralph, the versioning seems weird to me.
> >> I don't understand the reasoning of version number. Our version number
> >> doesn't have to be managed by some tweet or google links.
> >> 
> >> 
> >> On Wed, 24 Mar 2021 at 09:17, Ralph Goers 
> >> 
> >> wrote:
> >>> If I were a user and expected the feature to be in 3.7.0 then I would
> >>> certainly also expect it in 3.8.0. The only ways to avoid this are a)
> >> 
> >> stay
> >> 
> >>> on 3.6.x.x until the feature is available, b) specifically say the
> >> 
> >> promised
> >> 
> >>> features aren’t available yet.
> >>> 
> >>> That said I’m +0 on the version numbering.
> >>> 
> >>> Ralph
> >>> 
>  On Mar 22, 2021, at 3:09 PM, Robert Scholte 
> >>> 
> >>> wrote:
>  There were enough tweets and conference talks were I demonstrated the
> >>> 
> >>> idea behind build/consumer.
> >>> 
>  Of course the audience wanted to hear a version, so the best possible
> >>> 
> >>> answer was "most likely 3.7.0"
> >>> 
>  First Google hit: Maven 3.7 to Include Default Wrapper - InfoQ[1] and
> >>> 
> >>> you can find much more.
> >>> 
>  Several PMC members discussed about what would be the proper value, the
> >>> 
> >>> result was in the end 3.8.0.
> >>> 
>  Most important: it is beyond 3.6.3 and before 4.
>  
>  Robert
>  
>  [1] https://www.infoq.com/news/2020/04/maven-wrapper/
>  
>  On 22-3-2021 21:14:10, Elliotte Rusty Harold 
> >> 
> >> wrote:
>  I'm a weak -1 on this, solely because I don't find the reasoning for
>  not calling this 3.7.0 to be compelling. "Apache Maven 3.7.0 would be
>  the first release where you could optionally activate the
>  build/consumer feature. This version of this release has been renamed
>  to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the
>  next available minor version."
>  
>  Are we sure? I certainly didn't expect 3.7.0 to be the first release
>  where you could optionally activate the build/consumer feature. I
>  can't say I expected anything in particular for 3.7.0. Did Maven ever
>  promise there would be a 3.7.0 with this feature?
>  
>  If it were renamed 3.7.0 I'd be at +1.
>  
>  On Mon, Mar 22, 2021 at 7:40 PM Robert Scholte wrote:
> > Hi,
> > 
> > For the details about this release, please read
> >>> 
> >>> https://maven.apache.org/docs/3.8.0/release-notes.html
> >>> 
> > Also please provide feedback on the release notes. (as you know, these
> >>> 
> >>> are published separately from the release, so it doesn't have to block
> >> 
> >> the
> >> 
> >>> release itself)
> >>> 
> > We solved 5 issues:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922
> >> =12350003=Text>> 
> > There are still a couple of issues left in JIRA:
> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND
> >> %20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%
> >> 20DESC>> 
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1633/
> >> 
> >> 

Re: [VOTE] Release Apache Maven version 3.8.0

[Nick Stolwijk]

Also +1 (non-binding) for me. I ran a chocolatey upgrade and I also have
Maven 3.8.0.

nicks@DESKTOP-HHAT2G9 (voyager) ~
00:15:29 $ mvn --version
Apache Maven 3.8.0 (6aa1f4acf5d6323e9aa08b763cb9933dc96749b9)
Maven home: C:\ProgramData\chocolatey\lib\maven\apache-maven-3.8.0
Java version: 16, vendor: Oracle Corporation, runtime: C:\Program
Files\OpenJDK\jdk-16
Default locale: en_GB, platform encoding: UTF-8
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

It seems such installers are (too) quick to upgrade.

With regards,

Nick Stolwijk

~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~

Lord Baden-Powell


On Fri, Mar 26, 2021 at 12:05 AM Mark Derricutt  wrote:

> +1 non-binding from me, tho I have (potential) concerns.
>
> I’d missed seeing the emails about the release vote, but DID notice that
> Mac Homebrew had upgraded me magically to 3.8.0.
>
> Which led me to tweeting that it seemed the download page wasn’t updated (
> then a followup about home-brew jumping the gun):
>
> https://twitter.com/talios/status/1374188445380214784
>
> Carlo Cabrera responded that he reverted the change in Homebrew:
>
> https://twitter.com/carlocab_/status/1374230372112867330
>
> tho, anyone who happened to download the update, still has that update
> installed.
>
> Downloading the zip here, and checking:
>
> ~/Downloads/Download Sync/apache-maven-3.8.0 ❯ ./bin/mvn -version
> Apache Maven 3.8.0 (6aa1f4acf5d6323e9aa08b763cb9933dc96749b9)
> Maven home: /Users/amrk/Downloads/Download Sync/apache-maven-3.8.0
> Java version: 1.8.0_282, vendor: Azul Systems, Inc., runtime:
>
> /Users/amrk/.sdkman/candidates/java/8.0.282-zulu/zulu-8.jdk/Contents/Home/jre
> Default locale: en_NZ, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> ~/Downloads/Download Sync/apache-maven-3.8.0 took 3s ❯ mvn --version
> Apache Maven 3.8.0 (6aa1f4acf5d6323e9aa08b763cb9933dc96749b9)
> Maven home: /usr/local/Cellar/maven/3.8.0/libexec
> Java version: 1.8.0_282, vendor: Azul Systems, Inc., runtime:
>
> /Users/amrk/.sdkman/candidates/java/8.0.282-zulu/zulu-8.jdk/Contents/Home/jre
> Default locale: en_NZ, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
>
> both releases have the same SHA1 for the build - so in this instance I’m
> happy for a +1.
>
> Tho I wonder what the recourse would be if needing to respin the release -
> 3.8.1 version bump or?
>
> Is there anyway to prevent this happening again? ( Probably off-thread
> replies would be best ).
>
> Mark
>
>
>
>
> From: Tibor Digana  
> Reply: Maven Developers List  
> Date: 26 March 2021 at 8:05:51 AM
> To: Maven Developers List  
> Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
>
> here is mine +1.
> The amount of work means more for me than the version 3.7.0 we skipped. We
> can improve it in the future of course!
> Regarding the issues found with the Warning on the console, these issues
> can be fixed as always, right after.
> T
>
> On Mon, Mar 22, 2021 at 8:40 PM Robert Scholte 
> wrote:
>
> > Hi,
> >
> > For the details about this release, please read
> > https://maven.apache.org/docs/3.8.0/release-notes.html
> > Also please provide feedback on the release notes. (as you know, these
> are
> > published separately from the release, so it doesn't have to block the
> > release itself)
> >
> > We solved 5 issues:
> >
> >
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
> >
> > There are still a couple of issues left in JIRA:
> >
> >
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1633/
> >
> >
> >
>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
> >
> >
>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
> >
> >
> > Source release checksum(s):
> >
> > apache-maven-3.8.0-bin.zip sha512:
>
> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
>
> >
> > apache-maven-3.8.0-src.zip sha512:
>
> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
>
> >
> >
> > Staging site:
> > https://maven.apache.org/ref/3-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
>

Re: [VOTE] Release Apache Maven version 3.8.0

[Mark Derricutt]

+1 non-binding from me, tho I have (potential) concerns.

I’d missed seeing the emails about the release vote, but DID notice that
Mac Homebrew had upgraded me magically to 3.8.0.

Which led me to tweeting that it seemed the download page wasn’t updated (
then a followup about home-brew jumping the gun):

https://twitter.com/talios/status/1374188445380214784

Carlo Cabrera responded that he reverted the change in Homebrew:

https://twitter.com/carlocab_/status/1374230372112867330

tho, anyone who happened to download the update, still has that update
installed.

Downloading the zip here, and checking:

~/Downloads/Download Sync/apache-maven-3.8.0 ❯ ./bin/mvn -version
Apache Maven 3.8.0 (6aa1f4acf5d6323e9aa08b763cb9933dc96749b9)
Maven home: /Users/amrk/Downloads/Download Sync/apache-maven-3.8.0
Java version: 1.8.0_282, vendor: Azul Systems, Inc., runtime:
/Users/amrk/.sdkman/candidates/java/8.0.282-zulu/zulu-8.jdk/Contents/Home/jre
Default locale: en_NZ, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
~/Downloads/Download Sync/apache-maven-3.8.0 took 3s ❯ mvn --version
Apache Maven 3.8.0 (6aa1f4acf5d6323e9aa08b763cb9933dc96749b9)
Maven home: /usr/local/Cellar/maven/3.8.0/libexec
Java version: 1.8.0_282, vendor: Azul Systems, Inc., runtime:
/Users/amrk/.sdkman/candidates/java/8.0.282-zulu/zulu-8.jdk/Contents/Home/jre
Default locale: en_NZ, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"

both releases have the same SHA1 for the build - so in this instance I’m
happy for a +1.

Tho I wonder what the recourse would be if needing to respin the release -
3.8.1 version bump or?

Is there anyway to prevent this happening again? ( Probably off-thread
replies would be best ).

Mark




From: Tibor Digana  
Reply: Maven Developers List  
Date: 26 March 2021 at 8:05:51 AM
To: Maven Developers List  
Subject:  Re: [VOTE] Release Apache Maven version 3.8.0

here is mine +1.
The amount of work means more for me than the version 3.7.0 we skipped. We
can improve it in the future of course!
Regarding the issues found with the Warning on the console, these issues
can be fixed as always, right after.
T

On Mon, Mar 22, 2021 at 8:40 PM Robert Scholte 
wrote:

> Hi,
>
> For the details about this release, please read
> https://maven.apache.org/docs/3.8.0/release-notes.html
> Also please provide feedback on the release notes. (as you know, these
are
> published separately from the release, so it doesn't have to block the
> release itself)
>
> We solved 5 issues:
>
>
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
>
> There are still a couple of issues left in JIRA:
>
>
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1633/
>
>
>
https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
>
>
https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
>
>
> Source release checksum(s):
>
> apache-maven-3.8.0-bin.zip sha512:
b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e

>
> apache-maven-3.8.0-src.zip sha512:
51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893

>
>
> Staging site:
> https://maven.apache.org/ref/3-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

Re: [VOTE] Release Apache Maven version 3.8.0

[Tibor Digana]

here is mine +1.
The amount of work means more for me than the version 3.7.0 we skipped. We
can improve it in the future of course!
Regarding the issues found with the Warning on the console, these issues
can be fixed as always, right after.
T

On Mon, Mar 22, 2021 at 8:40 PM Robert Scholte  wrote:

> Hi,
>
> For the details about this release, please read
> https://maven.apache.org/docs/3.8.0/release-notes.html
> Also please provide feedback on the release notes. (as you know, these are
> published separately from the release, so it doesn't have to block the
> release itself)
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1633/
>
>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
>
>
> Source release checksum(s):
>
> apache-maven-3.8.0-bin.zip sha512: 
> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
>
> apache-maven-3.8.0-src.zip sha512: 
> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
>
>
> Staging site:
> https://maven.apache.org/ref/3-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

Re: [VOTE] Release Apache Maven version 3.8.0

[Maarten Mulders]

A 0-vote from my side. As far as I can tell, non-TLS repos are indeed 
blocked. That is the main reason for cutting this release, and it works, 
which is good.


But if I understood Hervé correctly, the message that appears when Maven 
attempts download of an artifact over a non-TLS connection differs 
depending on which component attempted the download. This has two 
consequences:


1. The message is sometimes pretty clear, but sometimes rather vague. An 
example of the latter one: "Checksum validation failed, expected Lorem 
but is a0a3234b13da255645808f53efb387d26ae441db". One must be quite 
clever to deduce that Maven attempted to download something over HTTP.


2. I am worried that we may have missed a component that also attempts 
to download artifacts, and still allows non-HTTP connections.



Maybe I didn't understand correctly - I actually hope so. In that case, 
please explain me where my understanding is wrong.


Thanks,


Maarten

On March 24th, 2021 at 18:54, Gary Gregory wrote:

Whenever I have to explain to colleagues that Maven "burns" version numbers
when a release candidate fails or some other obtuse reason, they are just
as baffled as I am. In the end it does not matter it's just bizarre.

Gary

On Tue, Mar 23, 2021, 20:58 Olivier Lamy  wrote:


+0
Same reason as Ralph, the versioning seems weird to me.
I don't understand the reasoning of version number. Our version number
doesn't have to be managed by some tweet or google links.


On Wed, 24 Mar 2021 at 09:17, Ralph Goers 
wrote:


If I were a user and expected the feature to be in 3.7.0 then I would
certainly also expect it in 3.8.0. The only ways to avoid this are a)

stay

on 3.6.x.x until the feature is available, b) specifically say the

promised

features aren’t available yet.

That said I’m +0 on the version numbering.

Ralph


On Mar 22, 2021, at 3:09 PM, Robert Scholte 

wrote:


There were enough tweets and conference talks were I demonstrated the

idea behind build/consumer.

Of course the audience wanted to hear a version, so the best possible

answer was "most likely 3.7.0"

First Google hit: Maven 3.7 to Include Default Wrapper - InfoQ[1] and

you can find much more.

Several PMC members discussed about what would be the proper value, the

result was in the end 3.8.0.

Most important: it is beyond 3.6.3 and before 4.

Robert

[1] https://www.infoq.com/news/2020/04/maven-wrapper/

On 22-3-2021 21:14:10, Elliotte Rusty Harold 

wrote:

I'm a weak -1 on this, solely because I don't find the reasoning for
not calling this 3.7.0 to be compelling. "Apache Maven 3.7.0 would be
the first release where you could optionally activate the
build/consumer feature. This version of this release has been renamed
to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the
next available minor version."

Are we sure? I certainly didn't expect 3.7.0 to be the first release
where you could optionally activate the build/consumer feature. I
can't say I expected anything in particular for 3.7.0. Did Maven ever
promise there would be a 3.7.0 with this feature?

If it were renamed 3.7.0 I'd be at +1.

On Mon, Mar 22, 2021 at 7:40 PM Robert Scholte wrote:


Hi,

For the details about this release, please read

https://maven.apache.org/docs/3.8.0/release-notes.html

Also please provide feedback on the release notes. (as you know, these

are published separately from the release, so it doesn't have to block

the

release itself)


We solved 5 issues:




https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text


There are still a couple of issues left in JIRA:




https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC


Staging repo:
https://repository.apache.org/content/repositories/maven-1633/





https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip





https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip



Source release checksum(s):
apache-maven-3.8.0-bin.zip sha512:



b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e

apache-maven-3.8.0-src.zip sha512:



51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893



Staging site:
https://maven.apache.org/ref/3-LATEST/

Guide to testing staged releases:


https://maven.apache.org/guides/development/guide-testing-releases.html


Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1




--
Elliotte Rusty Harold
elh...@ibiblio.org

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





-
To unsubscribe, e-mail: 

Re: [VOTE] Release Apache Maven version 3.8.0

[Gary Gregory]

Whenever I have to explain to colleagues that Maven "burns" version numbers
when a release candidate fails or some other obtuse reason, they are just
as baffled as I am. In the end it does not matter it's just bizarre.

Gary

On Tue, Mar 23, 2021, 20:58 Olivier Lamy  wrote:

> +0
> Same reason as Ralph, the versioning seems weird to me.
> I don't understand the reasoning of version number. Our version number
> doesn't have to be managed by some tweet or google links.
>
>
> On Wed, 24 Mar 2021 at 09:17, Ralph Goers 
> wrote:
>
> > If I were a user and expected the feature to be in 3.7.0 then I would
> > certainly also expect it in 3.8.0. The only ways to avoid this are a)
> stay
> > on 3.6.x.x until the feature is available, b) specifically say the
> promised
> > features aren’t available yet.
> >
> > That said I’m +0 on the version numbering.
> >
> > Ralph
> >
> > > On Mar 22, 2021, at 3:09 PM, Robert Scholte 
> > wrote:
> > >
> > > There were enough tweets and conference talks were I demonstrated the
> > idea behind build/consumer.
> > > Of course the audience wanted to hear a version, so the best possible
> > answer was "most likely 3.7.0"
> > > First Google hit: Maven 3.7 to Include Default Wrapper - InfoQ[1] and
> > you can find much more.
> > > Several PMC members discussed about what would be the proper value, the
> > result was in the end 3.8.0.
> > > Most important: it is beyond 3.6.3 and before 4.
> > >
> > > Robert
> > >
> > > [1] https://www.infoq.com/news/2020/04/maven-wrapper/
> > >
> > > On 22-3-2021 21:14:10, Elliotte Rusty Harold 
> wrote:
> > > I'm a weak -1 on this, solely because I don't find the reasoning for
> > > not calling this 3.7.0 to be compelling. "Apache Maven 3.7.0 would be
> > > the first release where you could optionally activate the
> > > build/consumer feature. This version of this release has been renamed
> > > to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the
> > > next available minor version."
> > >
> > > Are we sure? I certainly didn't expect 3.7.0 to be the first release
> > > where you could optionally activate the build/consumer feature. I
> > > can't say I expected anything in particular for 3.7.0. Did Maven ever
> > > promise there would be a 3.7.0 with this feature?
> > >
> > > If it were renamed 3.7.0 I'd be at +1.
> > >
> > > On Mon, Mar 22, 2021 at 7:40 PM Robert Scholte wrote:
> > >>
> > >> Hi,
> > >>
> > >> For the details about this release, please read
> > https://maven.apache.org/docs/3.8.0/release-notes.html
> > >> Also please provide feedback on the release notes. (as you know, these
> > are published separately from the release, so it doesn't have to block
> the
> > release itself)
> > >>
> > >> We solved 5 issues:
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
> > >>
> > >> There are still a couple of issues left in JIRA:
> > >>
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> > >>
> > >> Staging repo:
> > >> https://repository.apache.org/content/repositories/maven-1633/
> > >>
> > >>
> >
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
> > >>
> >
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
> > >>
> > >>
> > >> Source release checksum(s):
> > >> apache-maven-3.8.0-bin.zip sha512:
> >
> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
> > >> apache-maven-3.8.0-src.zip sha512:
> >
> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
> > >>
> > >>
> > >> Staging site:
> > >> https://maven.apache.org/ref/3-LATEST/
> > >>
> > >> Guide to testing staged releases:
> > >>
> https://maven.apache.org/guides/development/guide-testing-releases.html
> > >>
> > >> Vote open for at least 72 hours.
> > >>
> > >> [ ] +1
> > >> [ ] +0
> > >> [ ] -1
> > >
> > >
> > >
> > > --
> > > Elliotte Rusty Harold
> > > elh...@ibiblio.org
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

Re: [VOTE] Release Apache Maven version 3.8.0

[Brian Fox]

I'm +1. If the worst thing we can find to worry about is the version
number 3.7, 3.8, then it seems like we're close enough.

On Wed, Mar 24, 2021 at 3:11 AM Romain Manni-Bucau
 wrote:
>
> +0 cause of the versioning which is unexpected (but you know what? since it
> is a git tag we can drop it and recreate it since only the hash is used and
> not the name so we can do the 3.7.0 ;)).
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  |
> LinkedIn  | Book
> 
>
>
> Le mer. 24 mars 2021 à 07:47, Hervé BOUTEMY  a
> écrit :
>
> > you know what? now that the tag is done, we can't revert :)
> >
> > Le mercredi 24 mars 2021, 01:58:19 CET Olivier Lamy a écrit :
> > > +0
> > > Same reason as Ralph, the versioning seems weird to me.
> > > I don't understand the reasoning of version number. Our version number
> > > doesn't have to be managed by some tweet or google links.
> > >
> > >
> > > On Wed, 24 Mar 2021 at 09:17, Ralph Goers 
> > >
> > > wrote:
> > > > If I were a user and expected the feature to be in 3.7.0 then I would
> > > > certainly also expect it in 3.8.0. The only ways to avoid this are a)
> > stay
> > > > on 3.6.x.x until the feature is available, b) specifically say the
> > > > promised
> > > > features aren’t available yet.
> > > >
> > > > That said I’m +0 on the version numbering.
> > > >
> > > > Ralph
> > > >
> > > > > On Mar 22, 2021, at 3:09 PM, Robert Scholte 
> > > >
> > > > wrote:
> > > > > There were enough tweets and conference talks were I demonstrated the
> > > >
> > > > idea behind build/consumer.
> > > >
> > > > > Of course the audience wanted to hear a version, so the best possible
> > > >
> > > > answer was "most likely 3.7.0"
> > > >
> > > > > First Google hit: Maven 3.7 to Include Default Wrapper - InfoQ[1] and
> > > >
> > > > you can find much more.
> > > >
> > > > > Several PMC members discussed about what would be the proper value,
> > the
> > > >
> > > > result was in the end 3.8.0.
> > > >
> > > > > Most important: it is beyond 3.6.3 and before 4.
> > > > >
> > > > > Robert
> > > > >
> > > > > [1] https://www.infoq.com/news/2020/04/maven-wrapper/
> > > > >
> > > > > On 22-3-2021 21:14:10, Elliotte Rusty Harold 
> > wrote:
> > > > > I'm a weak -1 on this, solely because I don't find the reasoning for
> > > > > not calling this 3.7.0 to be compelling. "Apache Maven 3.7.0 would be
> > > > > the first release where you could optionally activate the
> > > > > build/consumer feature. This version of this release has been renamed
> > > > > to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the
> > > > > next available minor version."
> > > > >
> > > > > Are we sure? I certainly didn't expect 3.7.0 to be the first release
> > > > > where you could optionally activate the build/consumer feature. I
> > > > > can't say I expected anything in particular for 3.7.0. Did Maven ever
> > > > > promise there would be a 3.7.0 with this feature?
> > > > >
> > > > > If it were renamed 3.7.0 I'd be at +1.
> > > > >
> > > > > On Mon, Mar 22, 2021 at 7:40 PM Robert Scholte wrote:
> > > > >> Hi,
> > > > >>
> > > > >> For the details about this release, please read
> > > >
> > > > https://maven.apache.org/docs/3.8.0/release-notes.html
> > > >
> > > > >> Also please provide feedback on the release notes. (as you know,
> > these
> > > >
> > > > are published separately from the release, so it doesn't have to block
> > the
> > > > release itself)
> > > >
> > > > >> We solved 5 issues:
> > > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922;
> > > > version=12350003=Text>
> > > > >> There are still a couple of issues left in JIRA:
> > > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%
> > > >
> > 20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20
> > > > DESC>
> > > > >> Staging repo:
> > > > >> https://repository.apache.org/content/repositories/maven-1633/
> > > >
> > > >
> > https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/ap
> > > > ache-maven-3.8.0-bin.zip
> > > >
> > > >
> > https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apac
> > > > he-maven-3.8.0-src.zip>
> > > > >> Source release checksum(s):
> > > >
> > > > >> apache-maven-3.8.0-bin.zip sha512:
> > > >
> > b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d
> > > > 569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e>
> > > > >> apache-maven-3.8.0-src.zip sha512:
> > > >
> > 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502
> > > > 558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893>
> > > > >> Staging site:
> > > > >> https://maven.apache.org/ref/3-LATEST/
> > > > >>
> > > > >> Guide 

Re: [VOTE] Release Apache Maven version 3.8.0

[Romain Manni-Bucau]

+0 cause of the versioning which is unexpected (but you know what? since it
is a git tag we can drop it and recreate it since only the hash is used and
not the name so we can do the 3.7.0 ;)).

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



Le mer. 24 mars 2021 à 07:47, Hervé BOUTEMY  a
écrit :

> you know what? now that the tag is done, we can't revert :)
>
> Le mercredi 24 mars 2021, 01:58:19 CET Olivier Lamy a écrit :
> > +0
> > Same reason as Ralph, the versioning seems weird to me.
> > I don't understand the reasoning of version number. Our version number
> > doesn't have to be managed by some tweet or google links.
> >
> >
> > On Wed, 24 Mar 2021 at 09:17, Ralph Goers 
> >
> > wrote:
> > > If I were a user and expected the feature to be in 3.7.0 then I would
> > > certainly also expect it in 3.8.0. The only ways to avoid this are a)
> stay
> > > on 3.6.x.x until the feature is available, b) specifically say the
> > > promised
> > > features aren’t available yet.
> > >
> > > That said I’m +0 on the version numbering.
> > >
> > > Ralph
> > >
> > > > On Mar 22, 2021, at 3:09 PM, Robert Scholte 
> > >
> > > wrote:
> > > > There were enough tweets and conference talks were I demonstrated the
> > >
> > > idea behind build/consumer.
> > >
> > > > Of course the audience wanted to hear a version, so the best possible
> > >
> > > answer was "most likely 3.7.0"
> > >
> > > > First Google hit: Maven 3.7 to Include Default Wrapper - InfoQ[1] and
> > >
> > > you can find much more.
> > >
> > > > Several PMC members discussed about what would be the proper value,
> the
> > >
> > > result was in the end 3.8.0.
> > >
> > > > Most important: it is beyond 3.6.3 and before 4.
> > > >
> > > > Robert
> > > >
> > > > [1] https://www.infoq.com/news/2020/04/maven-wrapper/
> > > >
> > > > On 22-3-2021 21:14:10, Elliotte Rusty Harold 
> wrote:
> > > > I'm a weak -1 on this, solely because I don't find the reasoning for
> > > > not calling this 3.7.0 to be compelling. "Apache Maven 3.7.0 would be
> > > > the first release where you could optionally activate the
> > > > build/consumer feature. This version of this release has been renamed
> > > > to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the
> > > > next available minor version."
> > > >
> > > > Are we sure? I certainly didn't expect 3.7.0 to be the first release
> > > > where you could optionally activate the build/consumer feature. I
> > > > can't say I expected anything in particular for 3.7.0. Did Maven ever
> > > > promise there would be a 3.7.0 with this feature?
> > > >
> > > > If it were renamed 3.7.0 I'd be at +1.
> > > >
> > > > On Mon, Mar 22, 2021 at 7:40 PM Robert Scholte wrote:
> > > >> Hi,
> > > >>
> > > >> For the details about this release, please read
> > >
> > > https://maven.apache.org/docs/3.8.0/release-notes.html
> > >
> > > >> Also please provide feedback on the release notes. (as you know,
> these
> > >
> > > are published separately from the release, so it doesn't have to block
> the
> > > release itself)
> > >
> > > >> We solved 5 issues:
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922;
> > > version=12350003=Text>
> > > >> There are still a couple of issues left in JIRA:
> > >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%
> > >
> 20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20
> > > DESC>
> > > >> Staging repo:
> > > >> https://repository.apache.org/content/repositories/maven-1633/
> > >
> > >
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/ap
> > > ache-maven-3.8.0-bin.zip
> > >
> > >
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apac
> > > he-maven-3.8.0-src.zip>
> > > >> Source release checksum(s):
> > >
> > > >> apache-maven-3.8.0-bin.zip sha512:
> > >
> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d
> > > 569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e>
> > > >> apache-maven-3.8.0-src.zip sha512:
> > >
> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502
> > > 558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893>
> > > >> Staging site:
> > > >> https://maven.apache.org/ref/3-LATEST/
> > > >>
> > > >> Guide to testing staged releases:
> > > >>
> https://maven.apache.org/guides/development/guide-testing-releases.html
> > > >>
> > > >> Vote open for at least 72 hours.
> > > >>
> > > >> [ ] +1
> > > >> [ ] +0
> > > >> [ ] -1
> > > >
> > > > --
> > > > Elliotte Rusty Harold
> > > > elh...@ibiblio.org
> > > >
> > > > -
> > > > To unsubscribe, e-mail: 

Re: [VOTE] Release Apache Maven version 3.8.0

[Hervé BOUTEMY]

you know what? now that the tag is done, we can't revert :)

Le mercredi 24 mars 2021, 01:58:19 CET Olivier Lamy a écrit :
> +0
> Same reason as Ralph, the versioning seems weird to me.
> I don't understand the reasoning of version number. Our version number
> doesn't have to be managed by some tweet or google links.
> 
> 
> On Wed, 24 Mar 2021 at 09:17, Ralph Goers 
> 
> wrote:
> > If I were a user and expected the feature to be in 3.7.0 then I would
> > certainly also expect it in 3.8.0. The only ways to avoid this are a) stay
> > on 3.6.x.x until the feature is available, b) specifically say the
> > promised
> > features aren’t available yet.
> > 
> > That said I’m +0 on the version numbering.
> > 
> > Ralph
> > 
> > > On Mar 22, 2021, at 3:09 PM, Robert Scholte 
> > 
> > wrote:
> > > There were enough tweets and conference talks were I demonstrated the
> > 
> > idea behind build/consumer.
> > 
> > > Of course the audience wanted to hear a version, so the best possible
> > 
> > answer was "most likely 3.7.0"
> > 
> > > First Google hit: Maven 3.7 to Include Default Wrapper - InfoQ[1] and
> > 
> > you can find much more.
> > 
> > > Several PMC members discussed about what would be the proper value, the
> > 
> > result was in the end 3.8.0.
> > 
> > > Most important: it is beyond 3.6.3 and before 4.
> > > 
> > > Robert
> > > 
> > > [1] https://www.infoq.com/news/2020/04/maven-wrapper/
> > > 
> > > On 22-3-2021 21:14:10, Elliotte Rusty Harold  wrote:
> > > I'm a weak -1 on this, solely because I don't find the reasoning for
> > > not calling this 3.7.0 to be compelling. "Apache Maven 3.7.0 would be
> > > the first release where you could optionally activate the
> > > build/consumer feature. This version of this release has been renamed
> > > to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the
> > > next available minor version."
> > > 
> > > Are we sure? I certainly didn't expect 3.7.0 to be the first release
> > > where you could optionally activate the build/consumer feature. I
> > > can't say I expected anything in particular for 3.7.0. Did Maven ever
> > > promise there would be a 3.7.0 with this feature?
> > > 
> > > If it were renamed 3.7.0 I'd be at +1.
> > > 
> > > On Mon, Mar 22, 2021 at 7:40 PM Robert Scholte wrote:
> > >> Hi,
> > >> 
> > >> For the details about this release, please read
> > 
> > https://maven.apache.org/docs/3.8.0/release-notes.html
> > 
> > >> Also please provide feedback on the release notes. (as you know, these
> > 
> > are published separately from the release, so it doesn't have to block the
> > release itself)
> > 
> > >> We solved 5 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922;
> > version=12350003=Text> 
> > >> There are still a couple of issues left in JIRA:
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%
> > 20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20
> > DESC> 
> > >> Staging repo:
> > >> https://repository.apache.org/content/repositories/maven-1633/
> > 
> > https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/ap
> > ache-maven-3.8.0-bin.zip
> > 
> > https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apac
> > he-maven-3.8.0-src.zip> 
> > >> Source release checksum(s):
> > 
> > >> apache-maven-3.8.0-bin.zip sha512:
> > b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d
> > 569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e> 
> > >> apache-maven-3.8.0-src.zip sha512:
> > 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502
> > 558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893> 
> > >> Staging site:
> > >> https://maven.apache.org/ref/3-LATEST/
> > >> 
> > >> Guide to testing staged releases:
> > >> https://maven.apache.org/guides/development/guide-testing-releases.html
> > >> 
> > >> Vote open for at least 72 hours.
> > >> 
> > >> [ ] +1
> > >> [ ] +0
> > >> [ ] -1
> > > 
> > > --
> > > Elliotte Rusty Harold
> > > elh...@ibiblio.org
> > > 
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org





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

Re: [VOTE] Release Apache Maven version 3.8.0

[Olivier Lamy]

+0
Same reason as Ralph, the versioning seems weird to me.
I don't understand the reasoning of version number. Our version number
doesn't have to be managed by some tweet or google links.


On Wed, 24 Mar 2021 at 09:17, Ralph Goers 
wrote:

> If I were a user and expected the feature to be in 3.7.0 then I would
> certainly also expect it in 3.8.0. The only ways to avoid this are a) stay
> on 3.6.x.x until the feature is available, b) specifically say the promised
> features aren’t available yet.
>
> That said I’m +0 on the version numbering.
>
> Ralph
>
> > On Mar 22, 2021, at 3:09 PM, Robert Scholte 
> wrote:
> >
> > There were enough tweets and conference talks were I demonstrated the
> idea behind build/consumer.
> > Of course the audience wanted to hear a version, so the best possible
> answer was "most likely 3.7.0"
> > First Google hit: Maven 3.7 to Include Default Wrapper - InfoQ[1] and
> you can find much more.
> > Several PMC members discussed about what would be the proper value, the
> result was in the end 3.8.0.
> > Most important: it is beyond 3.6.3 and before 4.
> >
> > Robert
> >
> > [1] https://www.infoq.com/news/2020/04/maven-wrapper/
> >
> > On 22-3-2021 21:14:10, Elliotte Rusty Harold  wrote:
> > I'm a weak -1 on this, solely because I don't find the reasoning for
> > not calling this 3.7.0 to be compelling. "Apache Maven 3.7.0 would be
> > the first release where you could optionally activate the
> > build/consumer feature. This version of this release has been renamed
> > to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the
> > next available minor version."
> >
> > Are we sure? I certainly didn't expect 3.7.0 to be the first release
> > where you could optionally activate the build/consumer feature. I
> > can't say I expected anything in particular for 3.7.0. Did Maven ever
> > promise there would be a 3.7.0 with this feature?
> >
> > If it were renamed 3.7.0 I'd be at +1.
> >
> > On Mon, Mar 22, 2021 at 7:40 PM Robert Scholte wrote:
> >>
> >> Hi,
> >>
> >> For the details about this release, please read
> https://maven.apache.org/docs/3.8.0/release-notes.html
> >> Also please provide feedback on the release notes. (as you know, these
> are published separately from the release, so it doesn't have to block the
> release itself)
> >>
> >> We solved 5 issues:
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
> >>
> >> There are still a couple of issues left in JIRA:
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> >>
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/maven-1633/
> >>
> >>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
> >>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
> >>
> >>
> >> Source release checksum(s):
> >> apache-maven-3.8.0-bin.zip sha512:
> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
> >> apache-maven-3.8.0-src.zip sha512:
> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
> >>
> >>
> >> Staging site:
> >> https://maven.apache.org/ref/3-LATEST/
> >>
> >> Guide to testing staged releases:
> >> https://maven.apache.org/guides/development/guide-testing-releases.html
> >>
> >> Vote open for at least 72 hours.
> >>
> >> [ ] +1
> >> [ ] +0
> >> [ ] -1
> >
> >
> >
> > --
> > Elliotte Rusty Harold
> > elh...@ibiblio.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Release Apache Maven version 3.8.0

[Ralph Goers]

If I were a user and expected the feature to be in 3.7.0 then I would certainly 
also expect it in 3.8.0. The only ways to avoid this are a) stay on 3.6.x.x 
until the feature is available, b) specifically say the promised features 
aren’t available yet.

That said I’m +0 on the version numbering.

Ralph

> On Mar 22, 2021, at 3:09 PM, Robert Scholte  wrote:
> 
> There were enough tweets and conference talks were I demonstrated the idea 
> behind build/consumer.
> Of course the audience wanted to hear a version, so the best possible answer 
> was "most likely 3.7.0"
> First Google hit: Maven 3.7 to Include Default Wrapper - InfoQ[1] and you can 
> find much more.
> Several PMC members discussed about what would be the proper value, the 
> result was in the end 3.8.0.
> Most important: it is beyond 3.6.3 and before 4.
> 
> Robert
> 
> [1] https://www.infoq.com/news/2020/04/maven-wrapper/
> 
> On 22-3-2021 21:14:10, Elliotte Rusty Harold  wrote:
> I'm a weak -1 on this, solely because I don't find the reasoning for
> not calling this 3.7.0 to be compelling. "Apache Maven 3.7.0 would be
> the first release where you could optionally activate the
> build/consumer feature. This version of this release has been renamed
> to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the
> next available minor version."
> 
> Are we sure? I certainly didn't expect 3.7.0 to be the first release
> where you could optionally activate the build/consumer feature. I
> can't say I expected anything in particular for 3.7.0. Did Maven ever
> promise there would be a 3.7.0 with this feature?
> 
> If it were renamed 3.7.0 I'd be at +1.
> 
> On Mon, Mar 22, 2021 at 7:40 PM Robert Scholte wrote:
>> 
>> Hi,
>> 
>> For the details about this release, please read 
>> https://maven.apache.org/docs/3.8.0/release-notes.html
>> Also please provide feedback on the release notes. (as you know, these are 
>> published separately from the release, so it doesn't have to block the 
>> release itself)
>> 
>> We solved 5 issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
>> 
>> There are still a couple of issues left in JIRA:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>> 
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-1633/
>> 
>> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
>> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
>> 
>> 
>> Source release checksum(s):
>> apache-maven-3.8.0-bin.zip sha512: 
>> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
>> apache-maven-3.8.0-src.zip sha512: 
>> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
>> 
>> 
>> Staging site:
>> https://maven.apache.org/ref/3-LATEST/
>> 
>> Guide to testing staged releases:
>> https://maven.apache.org/guides/development/guide-testing-releases.html
>> 
>> Vote open for at least 72 hours.
>> 
>> [ ] +1
>> [ ] +0
>> [ ] -1
> 
> 
> 
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 



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

Re: [VOTE] Release Apache Maven version 3.8.0

[Hervé BOUTEMY]

after some review together, we identified that such basic error message happens 
when blocked HTTP repository is defined in build pom.xml
Ideally, we would need an enhanced error message like it happens when HTTP 
repository is defined in a dependency POM

Jira issue created for tracking that enhancement:
https://issues.apache.org/jira/browse/MNG-7128

Regards,

Hervé

Le mardi 23 mars 2021, 07:50:15 CET Hervé BOUTEMY a écrit :
> what "mvn" command are you running?
> can you send me the full logs, please?
> 
> Regards,
> 
> Hervé
> 
> Le lundi 22 mars 2021, 22:00:31 CET Maarten Mulders a écrit :
> > Tested on a MacBook, set up a HTTP (non-TLS) repository, and removed a
> > part of my ~/.m2/repository. The missing artifacts are not downloaded
> > 
> > over HTTP, which is good:
> >Downloading from maven-default-http-blocker: http://0.0.0.0/...
> >Downloading from maven-default-http-blocker: http://0.0.0.0/...
> > 
> > The logging and error message are a bit confusing for me though:
> >Checksum validation failed, expected Lorem but is
> > 
> > a0a3234b13da255645808f53efb387d26ae441db
> > 
> > 
> > See attachment for longer message and stacktrace.
> > Is that the expected type of logging in such situations?
> > 
> > I would say it doesn't make clear what the problem is (a repository with
> > HTTP) or what to do (contact administrator of repository, switch to
> > HTTPS if possible). Instead the message suggests a checksum failure but
> > that is not the real cause, is it?
> > 
> > Thanks,
> > 
> > 
> > Maarten
> > 
> > On March 22nd, 2021 at 21:36, Arnaud Héritier wrote:
> > > Well done team.
> > > 
> > > Not yet tested, I'll vote later.
> > > About the release note the link to the Repository Order
> > >  
> > > > > mu
> > > ltiple-repositories.html#repository-order> page
> > > is broken. I think it is because the link doesn't have the https://
> > > prefix/protocol)
> > > About the content and especially MNG-7117 and MNG-7118 do we have an
> > > update
> > > of https://maven.apache.org/guides/mini/guide-mirror-settings.html ? I
> > > see
> > > the code changes but I don't find the doc update. The release note maybe
> > > perhaps simplified to just say that we added 2 new features in the
> > > mirror
> > > configuration (the blocked element and the matching rule for http
> > > protocol)
> > > and we had a link to a more detailed doc
> > > 
> > > Elliotte I am not sure. I agree with you that nobody promised anything
> > > but
> > > if you google Maven 3.7.0 you can find many reference about the
> > > inclusion
> > > of the wrapper [1] or the build/consumer pom [2]
> > > In any case I don't think it will be clear for everyone.
> > > 
> > > [1] https://www.infoq.com/news/2020/04/maven-wrapper/
> > > [2]
> > > https://cwiki.apache.org/confluence/display/MAVEN/Build+vs+Consumer+POM
> > > Can be easily fixed.
> > > 
> > > cheers
> > > 
> > > On Mon, Mar 22, 2021 at 8:40 PM Robert Scholte 
> 
> wrote:
> > >> Hi,
> > >> 
> > >> For the details about this release, please read
> > >> https://maven.apache.org/docs/3.8.0/release-notes.html
> > >> Also please provide feedback on the release notes. (as you know, these
> > >> are
> > >> published separately from the release, so it doesn't have to block the
> > >> release itself)
> > >> 
> > >> We solved 5 issues:
> > >> 
> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123169
> > >> 22
> > >> =12350003=Text
> > >> 
> > >> There are still a couple of issues left in JIRA:
> > >> 
> > >> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20A
> > >> ND
> > >> %20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priorit
> > >> y%
> > >> 20DESC
> > >> 
> > >> Staging repo:
> > >> https://repository.apache.org/content/repositories/maven-1633/
> > >> 
> > >> 
> > >> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries
> > >> /a
> > >> pache-maven-3.8.0-bin.zip
> > >> 
> > >> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/a
> > >> pa
> > >> che-maven-3.8.0-src.zip
> > >> 
> > >> 
> > >> Source release checksum(s):
> > >> 
> > >> apache-maven-3.8.0-bin.zip sha512:
> > >> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a
> > >> 0
> > >> 1d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
> > >> 
> > >> apache-maven-3.8.0-src.zip sha512:
> > >> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76
> > >> 5
> > >> 02558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
> > >> 
> > >> 
> > >> Staging site:
> > >> https://maven.apache.org/ref/3-LATEST/
> > >> 
> > >> Guide to testing staged releases:
> > >> https://maven.apache.org/guides/development/guide-testing-releases.html
> > >> 
> > >> Vote open for at least 72 hours.
> > >> 
> > >> [ ] +1
> > >> [ ] +0
> > >> [ ] -1
> 
> -
> To 

Re: [VOTE] Release Apache Maven version 3.8.0

[Brian Fox]

The CVE is for documentation and the hardening of default behavior,
it's not your typical zero day.

On Mon, Mar 22, 2021 at 10:53 PM Gary Gregory  wrote:
>
> You are acknowledging a CVE _before_ a release?
>
> Gary
>
>
> On Mon, Mar 22, 2021, 15:40 Robert Scholte  wrote:
>
> > Hi,
> >
> > For the details about this release, please read
> > https://maven.apache.org/docs/3.8.0/release-notes.html
> > Also please provide feedback on the release notes. (as you know, these are
> > published separately from the release, so it doesn't have to block the
> > release itself)
> >
> > We solved 5 issues:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
> >
> > There are still a couple of issues left in JIRA:
> >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1633/
> >
> >
> > https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
> >
> > https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
> >
> >
> > Source release checksum(s):
> >
> > apache-maven-3.8.0-bin.zip sha512: 
> > b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
> >
> > apache-maven-3.8.0-src.zip sha512: 
> > 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
> >
> >
> > Staging site:
> > https://maven.apache.org/ref/3-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >

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

Re: [VOTE] Release Apache Maven version 3.8.0

[Hervé BOUTEMY]

what "mvn" command are you running?
can you send me the full logs, please?

Regards,

Hervé

Le lundi 22 mars 2021, 22:00:31 CET Maarten Mulders a écrit :
> Tested on a MacBook, set up a HTTP (non-TLS) repository, and removed a
> part of my ~/.m2/repository. The missing artifacts are not downloaded
> over HTTP, which is good:
> 
> 
>Downloading from maven-default-http-blocker: http://0.0.0.0/...
>Downloading from maven-default-http-blocker: http://0.0.0.0/...
> 
> 
> The logging and error message are a bit confusing for me though:
> 
> 
>Checksum validation failed, expected Lorem but is
> a0a3234b13da255645808f53efb387d26ae441db
> 
> 
> See attachment for longer message and stacktrace.
> Is that the expected type of logging in such situations?
> 
> I would say it doesn't make clear what the problem is (a repository with
> HTTP) or what to do (contact administrator of repository, switch to
> HTTPS if possible). Instead the message suggests a checksum failure but
> that is not the real cause, is it?
> 
> Thanks,
> 
> 
> Maarten
> 
> On March 22nd, 2021 at 21:36, Arnaud Héritier wrote:
> > Well done team.
> > 
> > Not yet tested, I'll vote later.
> > About the release note the link to the Repository Order
> >  > ltiple-repositories.html#repository-order> page
> > is broken. I think it is because the link doesn't have the https://
> > prefix/protocol)
> > About the content and especially MNG-7117 and MNG-7118 do we have an
> > update
> > of https://maven.apache.org/guides/mini/guide-mirror-settings.html ? I see
> > the code changes but I don't find the doc update. The release note maybe
> > perhaps simplified to just say that we added 2 new features in the mirror
> > configuration (the blocked element and the matching rule for http
> > protocol)
> > and we had a link to a more detailed doc
> > 
> > Elliotte I am not sure. I agree with you that nobody promised anything but
> > if you google Maven 3.7.0 you can find many reference about the inclusion
> > of the wrapper [1] or the build/consumer pom [2]
> > In any case I don't think it will be clear for everyone.
> > 
> > [1] https://www.infoq.com/news/2020/04/maven-wrapper/
> > [2]
> > https://cwiki.apache.org/confluence/display/MAVEN/Build+vs+Consumer+POM
> > Can be easily fixed.
> > 
> > cheers
> > 
> > On Mon, Mar 22, 2021 at 8:40 PM Robert Scholte  
wrote:
> >> Hi,
> >> 
> >> For the details about this release, please read
> >> https://maven.apache.org/docs/3.8.0/release-notes.html
> >> Also please provide feedback on the release notes. (as you know, these
> >> are
> >> published separately from the release, so it doesn't have to block the
> >> release itself)
> >> 
> >> We solved 5 issues:
> >> 
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922
> >> =12350003=Text
> >> 
> >> There are still a couple of issues left in JIRA:
> >> 
> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND
> >> %20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%
> >> 20DESC
> >> 
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/maven-1633/
> >> 
> >> 
> >> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/a
> >> pache-maven-3.8.0-bin.zip
> >> 
> >> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apa
> >> che-maven-3.8.0-src.zip
> >> 
> >> 
> >> Source release checksum(s):
> >> 
> >> apache-maven-3.8.0-bin.zip sha512:
> >> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a0
> >> 1d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
> >> 
> >> apache-maven-3.8.0-src.zip sha512:
> >> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c765
> >> 02558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
> >> 
> >> 
> >> Staging site:
> >> https://maven.apache.org/ref/3-LATEST/
> >> 
> >> Guide to testing staged releases:
> >> https://maven.apache.org/guides/development/guide-testing-releases.html
> >> 
> >> Vote open for at least 72 hours.
> >> 
> >> [ ] +1
> >> [ ] +0
> >> [ ] -1





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

Re: [VOTE] Release Apache Maven version 3.8.0

[Gary Gregory]

You are acknowledging a CVE _before_ a release?

Gary


On Mon, Mar 22, 2021, 15:40 Robert Scholte  wrote:

> Hi,
>
> For the details about this release, please read
> https://maven.apache.org/docs/3.8.0/release-notes.html
> Also please provide feedback on the release notes. (as you know, these are
> published separately from the release, so it doesn't have to block the
> release itself)
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1633/
>
>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
>
>
> Source release checksum(s):
>
> apache-maven-3.8.0-bin.zip sha512: 
> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
>
> apache-maven-3.8.0-src.zip sha512: 
> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
>
>
> Staging site:
> https://maven.apache.org/ref/3-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

Re: [VOTE] Release Apache Maven version 3.8.0

[Robert Scholte]

There were enough tweets and conference talks were I demonstrated the idea 
behind build/consumer.
Of course the audience wanted to hear a version, so the best possible answer 
was "most likely 3.7.0"
First Google hit: Maven 3.7 to Include Default Wrapper - InfoQ[1] and you can 
find much more.
Several PMC members discussed about what would be the proper value, the result 
was in the end 3.8.0.
Most important: it is beyond 3.6.3 and before 4.

Robert

[1] https://www.infoq.com/news/2020/04/maven-wrapper/

On 22-3-2021 21:14:10, Elliotte Rusty Harold  wrote:
I'm a weak -1 on this, solely because I don't find the reasoning for
not calling this 3.7.0 to be compelling. "Apache Maven 3.7.0 would be
the first release where you could optionally activate the
build/consumer feature. This version of this release has been renamed
to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the
next available minor version."

Are we sure? I certainly didn't expect 3.7.0 to be the first release
where you could optionally activate the build/consumer feature. I
can't say I expected anything in particular for 3.7.0. Did Maven ever
promise there would be a 3.7.0 with this feature?

If it were renamed 3.7.0 I'd be at +1.

On Mon, Mar 22, 2021 at 7:40 PM Robert Scholte wrote:
>
> Hi,
>
> For the details about this release, please read 
> https://maven.apache.org/docs/3.8.0/release-notes.html
> Also please provide feedback on the release notes. (as you know, these are 
> published separately from the release, so it doesn't have to block the 
> release itself)
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1633/
>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
>
>
> Source release checksum(s):
> apache-maven-3.8.0-bin.zip sha512: 
> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
> apache-maven-3.8.0-src.zip sha512: 
> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
>
>
> Staging site:
> https://maven.apache.org/ref/3-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



--
Elliotte Rusty Harold
elh...@ibiblio.org

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

Re: [VOTE] Release Apache Maven version 3.8.0

[Maarten Mulders]

Tested on a MacBook, set up a HTTP (non-TLS) repository, and removed a 
part of my ~/.m2/repository. The missing artifacts are not downloaded 
over HTTP, which is good:



  Downloading from maven-default-http-blocker: http://0.0.0.0/...
  Downloading from maven-default-http-blocker: http://0.0.0.0/...


The logging and error message are a bit confusing for me though:


  Checksum validation failed, expected Lorem but is 
a0a3234b13da255645808f53efb387d26ae441db



See attachment for longer message and stacktrace.
Is that the expected type of logging in such situations?

I would say it doesn't make clear what the problem is (a repository with 
HTTP) or what to do (contact administrator of repository, switch to 
HTTPS if possible). Instead the message suggests a checksum failure but 
that is not the real cause, is it?


Thanks,


Maarten


On March 22nd, 2021 at 21:36, Arnaud Héritier wrote:

Well done team.

Not yet tested, I'll vote later.
About the release note the link to the Repository Order

page
is broken. I think it is because the link doesn't have the https://
prefix/protocol)
About the content and especially MNG-7117 and MNG-7118 do we have an update
of https://maven.apache.org/guides/mini/guide-mirror-settings.html ? I see
the code changes but I don't find the doc update. The release note maybe
perhaps simplified to just say that we added 2 new features in the mirror
configuration (the blocked element and the matching rule for http protocol)
and we had a link to a more detailed doc

Elliotte I am not sure. I agree with you that nobody promised anything but
if you google Maven 3.7.0 you can find many reference about the inclusion
of the wrapper [1] or the build/consumer pom [2]
In any case I don't think it will be clear for everyone.

[1] https://www.infoq.com/news/2020/04/maven-wrapper/
[2] https://cwiki.apache.org/confluence/display/MAVEN/Build+vs+Consumer+POM
Can be easily fixed.

cheers



On Mon, Mar 22, 2021 at 8:40 PM Robert Scholte  wrote:


Hi,

For the details about this release, please read
https://maven.apache.org/docs/3.8.0/release-notes.html
Also please provide feedback on the release notes. (as you know, these are
published separately from the release, so it doesn't have to block the
release itself)

We solved 5 issues:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text

There are still a couple of issues left in JIRA:

https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1633/


https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip

https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip


Source release checksum(s):

apache-maven-3.8.0-bin.zip sha512: 
b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e

apache-maven-3.8.0-src.zip sha512: 
51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893


Staging site:
https://maven.apache.org/ref/3-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1




Downloading from maven-default-http-blocker: 
http://0.0.0.0/com/google/guava/guava/30.1-jre/guava-30.1-jre.jar
Downloading from maven-default-http-blocker: 
http://0.0.0.0/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar
[WARNING] Checksum validation failed, expected Lorem but is 
a0a3234b13da255645808f53efb387d26ae441db from maven-default-http-blocker for 
http://0.0.0.0/com/google/guava/guava/30.1-jre/guava-30.1-jre.jar
[WARNING] Checksum validation failed, expected Lorem but is 
a0a3234b13da255645808f53efb387d26ae441db from maven-default-http-blocker for 
http://0.0.0.0/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar
[WARNING] Could not validate integrity of download from 
http://0.0.0.0/com/google/guava/guava/30.1-jre/guava-30.1-jre.jar
org.eclipse.aether.transfer.ChecksumFailureException: Checksum validation 
failed, expected Lorem but is a0a3234b13da255645808f53efb387d26ae441db
at 
org.eclipse.aether.connector.basic.ChecksumValidator.validateExternalChecksums 
(ChecksumValidator.java:174)
at org.eclipse.aether.connector.basic.ChecksumValidator.validate 
(ChecksumValidator.java:103)
at 
org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask
 (BasicRepositoryConnector.java:460)
at 
org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run 
(BasicRepositoryConnector.java:364)
at 

Re: [VOTE] Release Apache Maven version 3.8.0

[Arnaud Héritier]

Well done team.

Not yet tested, I'll vote later.
About the release note the link to the Repository Order

page
is broken. I think it is because the link doesn't have the https://
prefix/protocol)
About the content and especially MNG-7117 and MNG-7118 do we have an update
of https://maven.apache.org/guides/mini/guide-mirror-settings.html ? I see
the code changes but I don't find the doc update. The release note maybe
perhaps simplified to just say that we added 2 new features in the mirror
configuration (the blocked element and the matching rule for http protocol)
and we had a link to a more detailed doc

Elliotte I am not sure. I agree with you that nobody promised anything but
if you google Maven 3.7.0 you can find many reference about the inclusion
of the wrapper [1] or the build/consumer pom [2]
In any case I don't think it will be clear for everyone.

[1] https://www.infoq.com/news/2020/04/maven-wrapper/
[2] https://cwiki.apache.org/confluence/display/MAVEN/Build+vs+Consumer+POM
Can be easily fixed.

cheers



On Mon, Mar 22, 2021 at 8:40 PM Robert Scholte  wrote:

> Hi,
>
> For the details about this release, please read
> https://maven.apache.org/docs/3.8.0/release-notes.html
> Also please provide feedback on the release notes. (as you know, these are
> published separately from the release, so it doesn't have to block the
> release itself)
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1633/
>
>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
>
>
> Source release checksum(s):
>
> apache-maven-3.8.0-bin.zip sha512: 
> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
>
> apache-maven-3.8.0-src.zip sha512: 
> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
>
>
> Staging site:
> https://maven.apache.org/ref/3-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>


-- 
Arnaud Héritier
Twitter/Skype : aheritier

Re: [VOTE] Release Apache Maven version 3.8.0

[Elliotte Rusty Harold]

I'm a weak -1 on this, solely because I don't find the reasoning for
not calling this 3.7.0 to be compelling. "Apache Maven 3.7.0 would be
the first release where you could optionally activate the
build/consumer feature. This version of this release has been renamed
to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the
next available minor version."

Are we sure? I certainly didn't expect 3.7.0 to be the first release
where you could optionally activate the build/consumer feature. I
can't say I expected anything in particular for 3.7.0. Did Maven ever
promise there would be a 3.7.0 with this feature?

If it were renamed 3.7.0 I'd be at +1.

On Mon, Mar 22, 2021 at 7:40 PM Robert Scholte  wrote:
>
> Hi,
>
> For the details about this release, please read 
> https://maven.apache.org/docs/3.8.0/release-notes.html
> Also please provide feedback on the release notes. (as you know, these are 
> published separately from the release, so it doesn't have to block the 
> release itself)
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1633/
>
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
> https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip
>
>
> Source release checksum(s):
> apache-maven-3.8.0-bin.zip sha512: 
> b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
> apache-maven-3.8.0-src.zip sha512: 
> 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893
>
>
> Staging site:
> https://maven.apache.org/ref/3-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 
Elliotte Rusty Harold
elh...@ibiblio.org

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

[VOTE] Release Apache Maven version 3.8.0

[Robert Scholte]

Hi,

For the details about this release, please read 
https://maven.apache.org/docs/3.8.0/release-notes.html
Also please provide feedback on the release notes. (as you know, these are 
published separately from the release, so it doesn't have to block the release 
itself)

We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1633/

https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip
https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip


Source release checksum(s):
apache-maven-3.8.0-bin.zip sha512: 
b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e
apache-maven-3.8.0-src.zip sha512: 
51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893


Staging site:
https://maven.apache.org/ref/3-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1