Apache does indeed have a Nexus staging area. See http://www.apache.org/dev/publishing-maven-artifacts.html
The instructions above are written for projects using Maven as the build system, so may of the details won’t work for us, but essentially the ‘deploy_river.groovy’ uploads the jar artifacts to the staging repository. In the past, we haven’t had many people using Maven to consume the artifacts, so I just did the staging and “release” (which moves the artifacts to the main Apache repository and then to Maven Central) after we had taken the release vote. But as the document above says, it’s perfectly OK to upload to the staging repository before the release vote. tl;dr; When you generate the release artifacts, run ‘deploy_river.groovy’ to stage the release candidates to the Apache staging repository, close the repository, then after the release vote, “release” the staged repository, or delete it if the vote fails for some reason. Cheers, Greg Trasuk > On Jan 11, 2016, at 9:55 PM, Patricia Shanahan <p...@acm.org> wrote: > > The actual wording of the relevant point in the release policy is: > > "During the process of developing software and preparing a release, > various packages are made available to the developer community for > testing purposes. Do not include any links on the project website that > might encourage non-developers to download and use nightly builds, > snapshots, release candidates, or any other similar package. The only > people who are supposed to know about such packages are the people > following the dev list (or searching its archives) and thus aware of the > conditions placed on the package. If you find that the general public > are downloading such test packages, then remove them." > > Staging something in a repository that is only discussed here and has to > be activated manually seems to me to be in accordance with the policy. > > On 1/11/2016 5:12 PM, Dan Rollo wrote: >> Just to clarify, I’m not talking about “releasing" anything in final >> form without a vote, but instead about “staging” candidate artifacts >> (with poms, etc) in a staging repository. This allows people to test >> the artifacts (and poms, etc) and various dependency declarations >> using the “staging” repository (which they would have to activate >> manually). Only after the staged artifacts are promoted (after votes >> pass, etc) would the artifacts be “released” (published to central). >> The “staged” items can easily be deleted if the vote does not pass, >> and/or if new items need to be restaged. >> >> >>> On Jan 11, 2016, at 6:55 PM, dev-digest-h...@river.apache.org >>> wrote: >>> >>> From: Peter <j...@zeus.net.au <mailto:j...@zeus.net.au>> Subject: >>> Re: River - 3.0.0 Release candidate Date: January 10, 2016 at >>> 1:34:44 AM EST To: dev@river.apache.org >>> <mailto:dev@river.apache.org> >>> >>> >>> I tend to agree, unfortunately we're not allowed to release >>> anything externally until after the release artifacts have been >>> voted on. >>> >>> On 10/01/2016 12:56 PM, Dan Rollo wrote: >>>> Do we have a process for staging the river artifacts in the maven >>>> central staging repo? And/or where do the related “pom.xml” files >>>> live (or get generated)? >>>> >>>> I tried to do some validation of the 3.0.0 jars using Dennis >>>> Reedy’s samples project on github, and ran into some dependency >>>> issues. Having staged artifacts/poms would clarify some >>>> dependency questions. >>>> >>>> Thanks, Dan >>>> >>>> >>>>>> On Jan 8, 2016, at 6:56 AM, Peter >>>>>> Firmstone<peter.firmst...@zeus.net.au >>>>>> <mailto:peter.firmst...@zeus.net.au><mailto:peter.firmst...@zeus.net.au >>>>>> <mailto:peter.firmst...@zeus.net.au>>> wrote: >>>>>> >>>>>> The Apache River 3.0.0 Release candidate is available here: >>>>>> >>>>>> http://people.apache.org/~peter_firmstone/<http://people.apache.org/~peter_firmstone/> >>>>>> <http://people.apache.org/~peter_firmstone/%3Chttp://people.apache.org/~peter_firmstone/%3E> >>>>>> >>>>>> >>>>>> > Voting on this release will commence in 4 weeks, to allow time for people to > check they can reproduce these artifacts and test their code and report back > with any issues. >>>>>> >>>>>> The code is currently in trunk, this will be branched after >>>>>> the 4 week review period and Voting passes. >>>>>> >>>>>> See also >>>>>> http://www.apache.org/dev/release-publishing.html<http://www.apache.org/dev/release-publishing.html> >>>>>> <http://www.apache.org/dev/release-publishing.html%3Chttp://www.apache.org/dev/release-publishing.html%3E> >>>>>> >>>>>> >>>>>> > Regards, >>>>>> >>>>>> Peter. >> >>
