[VOTE] Release Apache Maven version 3.8.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[VOTE] Release Apache Maven version 3.8.0

rfscholte
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&styleName=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
Reply | Threaded
Open this post in threaded view
|

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 <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>


Le mer. 24 mars 2021 à 07:47, Hervé BOUTEMY <[hidden email]> 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 <[hidden email]>
> >
> > 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 <[hidden email]>
> > >
> > > 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 <[hidden email]>
> 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&styleName=Text>
> > > >> There are still a couple of issues left in JIRA:
> > >
> <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%">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
> > > > [hidden email]
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Maven version 3.8.0

mthmulders
In reply to this post by rfscholte
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 <[hidden email]> 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 <[hidden email]>
>> 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 <[hidden email]>
>>> 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 <[hidden email]>
>> 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&styleName=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
>>>> [hidden email]
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>> --
>> Olivier Lamy
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Maven version 3.8.0

Mark Derricutt
In reply to this post by rfscholte
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 <[hidden email]> <[hidden email]>
Reply: Maven Developers List <[hidden email]> <[hidden email]>
Date: 26 March 2021 at 2:13:05 PM
To: Maven Developers List <[hidden email]> <[hidden email]>
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
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Maven version 3.8.0

Maxim Solodovnik
On Fri, 26 Mar 2021 at 14:24, Guillaume Nodet <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> <[hidden email]>
> > > > Reply: Maven Developers List <[hidden email]> <
> > [hidden email]>
> > > > Date: 26 March 2021 at 2:13:05 PM
> > > > To: Maven Developers List <[hidden email]> <[hidden email]
> > >
> > > > 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: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> --
> ------------------------
> Guillaume Nodet



--
Best regards,
Maxim

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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 <[hidden email]>
wrote:

> On Fri, 26 Mar 2021 at 14:24, Guillaume Nodet <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]>
> 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 <[hidden email]> <
> [hidden email]>
> > > > > Reply: Maven Developers List <[hidden email]> <
> > > [hidden email]>
> > > > > Date: 26 March 2021 at 2:13:05 PM
> > > > > To: Maven Developers List <[hidden email]> <
> [hidden email]
> > > >
> > > > > 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: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
> > --
> > ------------------------
> > Guillaume Nodet
>
>
>
> --
> Best regards,
> Maxim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> --
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Reply | Threaded
Open this post in threaded view
|

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 <[hidden email]> <[hidden email]>
Reply: Maven Developers List <[hidden email]> <[hidden email]>
Date: 27 March 2021 at 2:19:48 PM
To: Maven Developers List <[hidden email]> <[hidden email]>
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