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.
