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 <[email protected]> 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 > > ries/apache-maven%E2%80%933.8.0-bin.zip> > > > > > > < > > > > http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/bina > > ries/apache-maven%E2%80%933.8.0-bin.zip> > > > > > > < > > > > http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/bina > > ries/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 < > > > > [email protected]> > > > > > > > > Reply: Maven Developers List < > > > > > > > > [email protected]> > > > > > > > > > > Date: 26 March 2021 at 2:13:05 PM > > > > > > To: Maven Developers List < > > > > [email protected] > > > > > > > > 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: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > -- > > > ------------------------ > > > Guillaume Nodet > > > > -- > > Best regards, > > Maxim > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > -- > > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
