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 <solomax...@gmail.com> 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 <ol...@apache.org> 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 <m...@talios.com> 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> <garydgreg...@gmail.com> > > > Reply: Maven Developers List <dev@maven.apache.org> < > dev@maven.apache.org> > > > Date: 26 March 2021 at 2:13:05 PM > > > To: Maven Developers List <dev@maven.apache.org> <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
