On Thu, Apr 4, 2013 at 1:30 PM, Matt Franklin <m.ben.franklin@gmail.com>wrote:
> I think we should keep going with the master pom release. We will need to
> close the current repository and re-create the staging with just the pom
> artifact, but there should be no reason why we can't release that
> separately while we wait for the 0.21.1 project release to get ready to go.
>
+1 - That will greatly simplify the 0.21.1 release anyway.
>
>
> On Thu, Apr 4, 2013 at 1:45 PM, Raminderjeet Singh <ramifnu@indiana.edu
> >wrote:
>
> > Vote is canceled. There are issues with mongodb backend and few other
> > issues reported on JIRA and dev list.
> >
> >
> > On Wed, Apr 3, 2013 at 2:27 PM, Raminder Singh <raminderjsingh@gmail.com
> > >wrote:
> >
> > > I've created a combined 0.21 release candidate, with the
> > > following artifacts up for a vote:
> > >
> > > SVN source tag (r1463751):
> > > https://svn.apache.org/repos/asf/rave/rave-master-pom/tags/0.21
> > >
> > > SVN source tag (r1463817):
> > > https://svn.apache.org/repos/asf/rave/tags/0.21
> > >
> > > Maven staging repo:
> > > https://repository.apache.org/content/repositories/orgapacherave-054/
> > >
> > > Source releases:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacherave-054/org/apache/rave/rave-master/0.21/rave-master-0.21-source-release.zip
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacherave-054/org/apache/rave/rave-project/0.21/rave-project-0.21-source-release.zip
> > >
> > > Demo Artifacts
> > > http://people.apache.org/builds/rave/0.21/apache-rave-0.21-bin.tar.gz
> > > http://people.apache.org/builds/rave/0.21/apache-rave-0.21-bin.zip
> > >
> > > PGP release keys (signed using 1BE72138):
> > > https://svn.apache.org/repos/asf/rave/KEYS
> > >
> > > Please take the time to verify the artifacts before casting your vote.
> > >
> > > Vote will be open for 72 hours.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> >
>
|