That's the normal release process for any project AFAIK, if you want to put a release candidate out to on https://dist.apache.org/repos/dist/dev/ that is done via svn, we've automated those steps.
Then the actual release goes to https://dist.apache.org/repos/dist/release/, same for Maven https://dist.apache.org/repos/dist/release/maven/ After that, the files are mirrored all over by various servers. Publishing to Maven Central is a separate process but critical since that is what most builds (Maven, Ant Ivy, and so on) expect and use. Gary On Sun, Oct 24, 2021, 05:27 Slawomir Jaranowski <s.jaranow...@gmail.com> wrote: > Hi, > > Very strange release process for common components ... some of the > artifacts are published to the Central Repository and some of them are > published by svn repository ... > I don't see benefit for customizing maven core for one of case of usage > > but it is discussion for another place, here I only point it > > > sob., 23 paź 2021 o 22:51 Gary Gregory <garydgreg...@gmail.com> > napisał(a): > > > HI All: > > > > I discovered a regression this morning that prevents me from creating > > a release candidate for Apache Commons CLI: > > > > https://issues.apache.org/jira/browse/MNG-7316 > > https://github.com/apache/maven/pull/601 > > > > May this be included for 3.8.4 please? > > > > Gary > > > > On Sat, Oct 23, 2021 at 3:48 PM Falko Modler <f.mod...@gmx.net> wrote: > > > > > > Hi, > > > > > > > Given that we had two releases with regressions I tend *not* to merge > > > > #578. Give it more time and thought. > > > > > > As written before on GH, not merging #578 or a backport of #476 will > > > bring back MNG-6843. > > > This will catch users off guard that were happily benefitting from > > > MNG-6843 being fixed in 3.8.2 and 3.8.3. > > > > > > If you still want to do it this way, then please at least document that > > > MNG-6843 is back under "Known Issues" in 3.8.4 "Release Notes". > > > Additionally, MNG-6843 should be reopened. > > > > > > I'd really prefer if we could keep MNG-6843 fixed, by whichever PR > > > (doesn't need to be mine). > > > > > > Cheers, > > > > > > Falko > > > > > > Am 23.10.2021 um 21:22 schrieb Michael Osipov: > > > > Folks, > > > > > > > > all important tickets for Maven 3.8.4 have been addressed in > > > > maven-3.8.x branch. > > > > > > > > We have two open PRs: > > > > * #578: Alternative to the ThreadLocal approach > > > > * #476: As far as I understand a more global approach to the issue > and > > > > supersedes #576, but requires Java 8. So Maven 3.9+ > > > > > > > > Given that we had two releases with regressions I tend *not* to merge > > > > #578. Give it more time and thought. Maybe go over to #476 directly > in > > > > 3.9.0 and 4.0.0. > > > > > > > > Please test and let me know whether you still see errors. If I don't > > > > read any objections I will start the new release somewhere around mid > > > > next week. > > > > > > > > Michael > > > > > > > > --------------------------------------------------------------------- > > > > 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 > > > > > > -- > Sławomir Jaranowski >
