You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by Raminder Singh <ra...@gmail.com> on 2013/04/03 20:27:20 UTC
[VOTE] Apache Rave 0.21 Release Candidate
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)
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Raminder Singh <ra...@gmail.com>.
Sure, I will do that this afternoon. Got busy with some other work.
Raminder
On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
>
>> 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.
>>
>
> Please start a new vote then for the master pom.
>
>
>>
>>>
>>>
>>> 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)
>>>>>
>>>>
>>>
>>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Raminder Singh <ra...@gmail.com>.
Sure, i will send out the master release vote asap.
Thanks
Raminder
On Apr 9, 2013, at 11:15 AM, Matt Franklin wrote:
> On Tuesday, April 9, 2013, Jasha Joachimsthal wrote:
>
>> It depends whether you expect to make a 0.21.1 release of the project
>> before this weekend. If you do, wait with the master pom and do a combined
>> release. Otherwise create a new release of only the master pom and start a
>> vote for it asap.
>
>
> I think Ate proposed that the developer metadata in master Pom be
> considered less important. The DOAP file should be kept up to date though.
>
> No offense to Erin, but I say make a release now.
>
>
>
>>
>> If you expect to do a 0.21.1 release of the project within ±72 hours from
>> now,
>>
>> On 9 April 2013 17:05, Raminder Singh <ra...@gmail.com> wrote:
>>
>>> I am checking again. Is it ok to send a rave master release without
>> Erin's
>>> name committed to the pom? He committed it now but its not part of the
>> tag.
>>> Do we want to do 0.21.1 for master also.
>>>
>>> Thanks
>>> Raminder
>>> On Apr 6, 2013, at 6:58 PM, Erin Noe-Payne wrote:
>>>
>>>> I've gone ahead and added my name & committed.
>>>>
>>>> On Fri, Apr 5, 2013 at 4:27 PM, Raminder Singh <
>> raminderjsingh@gmail.com>
>>> wrote:
>>>>> I moved to discussion thread.
>>>>>
>>>>> You can checkout
>>> https://svn.apache.org/repos/asf/rave/rave-master-pom/trunk and add your
>>> info to pom. I am not sure if its required for the release. Just want to
>>> check with others before start the vote thread for master.
>>>>>
>>>>> Thanks
>>>>> Raminder
>>>>>
>>>>> On Apr 5, 2013, at 4:23 PM, Erin Noe-Payne wrote:
>>>>>
>>>>>> Sure. What do I need to do?
>>>>>>
>>>>>> On Fri, Apr 5, 2013 at 4:19 PM, Raminder Singh <
>>> raminderjsingh@gmail.com> wrote:
>>>>>>> I just noticed, Erin is still not added to master pom as committer
>>> and PMC. Do we want to do that before 0.21 master release?
>>>>>>>
>>>>>>> Thanks
>>>>>>> Raminder
>>>>>>> On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
>>>>>>>
>>>>>>>> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
>>>>>>>>
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Please start a new vote then for the master pom.
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 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
>>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Jasha Joachimsthal <ja...@apache.org>.
On 9 April 2013 17:15, Matt Franklin <m....@gmail.com> wrote:
> On Tuesday, April 9, 2013, Jasha Joachimsthal wrote:
>
> > It depends whether you expect to make a 0.21.1 release of the project
> > before this weekend. If you do, wait with the master pom and do a
> combined
> > release. Otherwise create a new release of only the master pom and start
> a
> > vote for it asap.
>
>
> I think Ate proposed that the developer metadata in master Pom be
> considered less important. The DOAP file should be kept up to date though.
>
> No offense to Erin, but I say make a release now.
>
You can't release without votes, right? And there hasn't been a separate
vote for the master pom yet.
>
>
> >
> > If you expect to do a 0.21.1 release of the project within ±72 hours from
> > now,
> >
> > On 9 April 2013 17:05, Raminder Singh <ra...@gmail.com> wrote:
> >
> > > I am checking again. Is it ok to send a rave master release without
> > Erin's
> > > name committed to the pom? He committed it now but its not part of the
> > tag.
> > > Do we want to do 0.21.1 for master also.
> > >
> > > Thanks
> > > Raminder
> > > On Apr 6, 2013, at 6:58 PM, Erin Noe-Payne wrote:
> > >
> > > > I've gone ahead and added my name & committed.
> > > >
> > > > On Fri, Apr 5, 2013 at 4:27 PM, Raminder Singh <
> > raminderjsingh@gmail.com>
> > > wrote:
> > > >> I moved to discussion thread.
> > > >>
> > > >> You can checkout
> > > https://svn.apache.org/repos/asf/rave/rave-master-pom/trunk and add
> your
> > > info to pom. I am not sure if its required for the release. Just want
> to
> > > check with others before start the vote thread for master.
> > > >>
> > > >> Thanks
> > > >> Raminder
> > > >>
> > > >> On Apr 5, 2013, at 4:23 PM, Erin Noe-Payne wrote:
> > > >>
> > > >>> Sure. What do I need to do?
> > > >>>
> > > >>> On Fri, Apr 5, 2013 at 4:19 PM, Raminder Singh <
> > > raminderjsingh@gmail.com> wrote:
> > > >>>> I just noticed, Erin is still not added to master pom as committer
> > > and PMC. Do we want to do that before 0.21 master release?
> > > >>>>
> > > >>>> Thanks
> > > >>>> Raminder
> > > >>>> On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
> > > >>>>
> > > >>>>> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
> > > >>>>>
> > > >>>>>> 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.
> > > >>>>>>
> > > >>>>>
> > > >>>>> Please start a new vote then for the master pom.
> > > >>>>>
> > > >>>>>
> > > >>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> 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
> >
>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Matt Franklin <m....@gmail.com>.
On Tuesday, April 9, 2013, Jasha Joachimsthal wrote:
> It depends whether you expect to make a 0.21.1 release of the project
> before this weekend. If you do, wait with the master pom and do a combined
> release. Otherwise create a new release of only the master pom and start a
> vote for it asap.
I think Ate proposed that the developer metadata in master Pom be
considered less important. The DOAP file should be kept up to date though.
No offense to Erin, but I say make a release now.
>
> If you expect to do a 0.21.1 release of the project within ±72 hours from
> now,
>
> On 9 April 2013 17:05, Raminder Singh <ra...@gmail.com> wrote:
>
> > I am checking again. Is it ok to send a rave master release without
> Erin's
> > name committed to the pom? He committed it now but its not part of the
> tag.
> > Do we want to do 0.21.1 for master also.
> >
> > Thanks
> > Raminder
> > On Apr 6, 2013, at 6:58 PM, Erin Noe-Payne wrote:
> >
> > > I've gone ahead and added my name & committed.
> > >
> > > On Fri, Apr 5, 2013 at 4:27 PM, Raminder Singh <
> raminderjsingh@gmail.com>
> > wrote:
> > >> I moved to discussion thread.
> > >>
> > >> You can checkout
> > https://svn.apache.org/repos/asf/rave/rave-master-pom/trunk and add your
> > info to pom. I am not sure if its required for the release. Just want to
> > check with others before start the vote thread for master.
> > >>
> > >> Thanks
> > >> Raminder
> > >>
> > >> On Apr 5, 2013, at 4:23 PM, Erin Noe-Payne wrote:
> > >>
> > >>> Sure. What do I need to do?
> > >>>
> > >>> On Fri, Apr 5, 2013 at 4:19 PM, Raminder Singh <
> > raminderjsingh@gmail.com> wrote:
> > >>>> I just noticed, Erin is still not added to master pom as committer
> > and PMC. Do we want to do that before 0.21 master release?
> > >>>>
> > >>>> Thanks
> > >>>> Raminder
> > >>>> On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
> > >>>>
> > >>>>> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
> > >>>>>
> > >>>>>> 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.
> > >>>>>>
> > >>>>>
> > >>>>> Please start a new vote then for the master pom.
> > >>>>>
> > >>>>>
> > >>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 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
>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Matt Franklin <m....@gmail.com>.
On Tuesday, April 9, 2013, Raminder Singh wrote:
> There are still open issues need to be addressed for 0.21.1 (RAVE-924). I
> don't think the release will be in 72 hours. New means creating a new tag
> and doing a release or using the existing tag?
The existing tag is what I propose
>
>
> On Apr 9, 2013, at 11:11 AM, Jasha Joachimsthal wrote:
>
> > It depends whether you expect to make a 0.21.1 release of the project
> > before this weekend. If you do, wait with the master pom and do a
> combined
> > release. Otherwise create a new release of only the master pom and start
> a
> > vote for it asap.
> >
> > If you expect to do a 0.21.1 release of the project within ±72 hours from
> > now,
> >
> > On 9 April 2013 17:05, Raminder Singh <ra...@gmail.com> wrote:
> >
> >> I am checking again. Is it ok to send a rave master release without
> Erin's
> >> name committed to the pom? He committed it now but its not part of the
> tag.
> >> Do we want to do 0.21.1 for master also.
> >>
> >> Thanks
> >> Raminder
> >> On Apr 6, 2013, at 6:58 PM, Erin Noe-Payne wrote:
> >>
> >>> I've gone ahead and added my name & committed.
> >>>
> >>> On Fri, Apr 5, 2013 at 4:27 PM, Raminder Singh <
> raminderjsingh@gmail.com>
> >> wrote:
> >>>> I moved to discussion thread.
> >>>>
> >>>> You can checkout
> >> https://svn.apache.org/repos/asf/rave/rave-master-pom/trunk and add
> your
> >> info to pom. I am not sure if its required for the release. Just want to
> >> check with others before start the vote thread for master.
> >>>>
> >>>> Thanks
> >>>> Raminder
> >>>>
> >>>> On Apr 5, 2013, at 4:23 PM, Erin Noe-Payne wrote:
> >>>>
> >>>>> Sure. What do I need to do?
> >>>>>
> >>>>> On Fri, Apr 5, 2013 at 4:19 PM, Raminder Singh <
> >> raminderjsingh@gmail.com> wrote:
> >>>>>> I just noticed, Erin is still not added to master pom as committer
> >> and PMC. Do we want to do that before 0.21 master release?
> >>>>>>
> >>>>>> Thanks
> >>>>>> Raminder
> >>>>>> On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
> >>>>>>
> >>>>>>> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
> >>>>>>>
> >>>>>>>> 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.
> >>>>>>>>
> >>>>>>>
> >>>>>>> Please start a new vote then for the master pom.
> >>>>>>>
> >>>>>>>
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> 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 <
> >>>>>>>>
Re: [DISCUSS] Apache Rave 0.21 Release Candidate
Posted by Raminder Singh <ra...@gmail.com>.
There are still open issues need to be addressed for 0.21.1 (RAVE-924). I don't think the release will be in 72 hours. New means creating a new tag and doing a release or using the existing tag?
On Apr 9, 2013, at 11:11 AM, Jasha Joachimsthal wrote:
> It depends whether you expect to make a 0.21.1 release of the project
> before this weekend. If you do, wait with the master pom and do a combined
> release. Otherwise create a new release of only the master pom and start a
> vote for it asap.
>
> If you expect to do a 0.21.1 release of the project within ±72 hours from
> now,
>
> On 9 April 2013 17:05, Raminder Singh <ra...@gmail.com> wrote:
>
>> I am checking again. Is it ok to send a rave master release without Erin's
>> name committed to the pom? He committed it now but its not part of the tag.
>> Do we want to do 0.21.1 for master also.
>>
>> Thanks
>> Raminder
>> On Apr 6, 2013, at 6:58 PM, Erin Noe-Payne wrote:
>>
>>> I've gone ahead and added my name & committed.
>>>
>>> On Fri, Apr 5, 2013 at 4:27 PM, Raminder Singh <ra...@gmail.com>
>> wrote:
>>>> I moved to discussion thread.
>>>>
>>>> You can checkout
>> https://svn.apache.org/repos/asf/rave/rave-master-pom/trunk and add your
>> info to pom. I am not sure if its required for the release. Just want to
>> check with others before start the vote thread for master.
>>>>
>>>> Thanks
>>>> Raminder
>>>>
>>>> On Apr 5, 2013, at 4:23 PM, Erin Noe-Payne wrote:
>>>>
>>>>> Sure. What do I need to do?
>>>>>
>>>>> On Fri, Apr 5, 2013 at 4:19 PM, Raminder Singh <
>> raminderjsingh@gmail.com> wrote:
>>>>>> I just noticed, Erin is still not added to master pom as committer
>> and PMC. Do we want to do that before 0.21 master release?
>>>>>>
>>>>>> Thanks
>>>>>> Raminder
>>>>>> On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
>>>>>>
>>>>>>> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
>>>>>>>
>>>>>>>> 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.
>>>>>>>>
>>>>>>>
>>>>>>> Please start a new vote then for the master pom.
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 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)
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>
>>
Re: [DISCUSS] Apache Rave 0.21 Release Candidate
Posted by Jasha Joachimsthal <ja...@apache.org>.
It depends whether you expect to make a 0.21.1 release of the project
before this weekend. If you do, wait with the master pom and do a combined
release. Otherwise create a new release of only the master pom and start a
vote for it asap.
If you expect to do a 0.21.1 release of the project within ±72 hours from
now,
On 9 April 2013 17:05, Raminder Singh <ra...@gmail.com> wrote:
> I am checking again. Is it ok to send a rave master release without Erin's
> name committed to the pom? He committed it now but its not part of the tag.
> Do we want to do 0.21.1 for master also.
>
> Thanks
> Raminder
> On Apr 6, 2013, at 6:58 PM, Erin Noe-Payne wrote:
>
> > I've gone ahead and added my name & committed.
> >
> > On Fri, Apr 5, 2013 at 4:27 PM, Raminder Singh <ra...@gmail.com>
> wrote:
> >> I moved to discussion thread.
> >>
> >> You can checkout
> https://svn.apache.org/repos/asf/rave/rave-master-pom/trunk and add your
> info to pom. I am not sure if its required for the release. Just want to
> check with others before start the vote thread for master.
> >>
> >> Thanks
> >> Raminder
> >>
> >> On Apr 5, 2013, at 4:23 PM, Erin Noe-Payne wrote:
> >>
> >>> Sure. What do I need to do?
> >>>
> >>> On Fri, Apr 5, 2013 at 4:19 PM, Raminder Singh <
> raminderjsingh@gmail.com> wrote:
> >>>> I just noticed, Erin is still not added to master pom as committer
> and PMC. Do we want to do that before 0.21 master release?
> >>>>
> >>>> Thanks
> >>>> Raminder
> >>>> On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
> >>>>
> >>>>> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
> >>>>>
> >>>>>> 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.
> >>>>>>
> >>>>>
> >>>>> Please start a new vote then for the master pom.
> >>>>>
> >>>>>
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> 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)
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>
> >>
>
>
Re: [DISCUSS] Apache Rave 0.21 Release Candidate
Posted by Raminder Singh <ra...@gmail.com>.
I am checking again. Is it ok to send a rave master release without Erin's name committed to the pom? He committed it now but its not part of the tag. Do we want to do 0.21.1 for master also.
Thanks
Raminder
On Apr 6, 2013, at 6:58 PM, Erin Noe-Payne wrote:
> I've gone ahead and added my name & committed.
>
> On Fri, Apr 5, 2013 at 4:27 PM, Raminder Singh <ra...@gmail.com> wrote:
>> I moved to discussion thread.
>>
>> You can checkout https://svn.apache.org/repos/asf/rave/rave-master-pom/trunk and add your info to pom. I am not sure if its required for the release. Just want to check with others before start the vote thread for master.
>>
>> Thanks
>> Raminder
>>
>> On Apr 5, 2013, at 4:23 PM, Erin Noe-Payne wrote:
>>
>>> Sure. What do I need to do?
>>>
>>> On Fri, Apr 5, 2013 at 4:19 PM, Raminder Singh <ra...@gmail.com> wrote:
>>>> I just noticed, Erin is still not added to master pom as committer and PMC. Do we want to do that before 0.21 master release?
>>>>
>>>> Thanks
>>>> Raminder
>>>> On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
>>>>
>>>>> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
>>>>>
>>>>>> 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.
>>>>>>
>>>>>
>>>>> Please start a new vote then for the master pom.
>>>>>
>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 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)
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>
Re: [DISCUSS] Apache Rave 0.21 Release Candidate
Posted by Erin Noe-Payne <er...@gmail.com>.
I've gone ahead and added my name & committed.
On Fri, Apr 5, 2013 at 4:27 PM, Raminder Singh <ra...@gmail.com> wrote:
> I moved to discussion thread.
>
> You can checkout https://svn.apache.org/repos/asf/rave/rave-master-pom/trunk and add your info to pom. I am not sure if its required for the release. Just want to check with others before start the vote thread for master.
>
> Thanks
> Raminder
>
> On Apr 5, 2013, at 4:23 PM, Erin Noe-Payne wrote:
>
>> Sure. What do I need to do?
>>
>> On Fri, Apr 5, 2013 at 4:19 PM, Raminder Singh <ra...@gmail.com> wrote:
>>> I just noticed, Erin is still not added to master pom as committer and PMC. Do we want to do that before 0.21 master release?
>>>
>>> Thanks
>>> Raminder
>>> On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
>>>
>>>> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
>>>>
>>>>> 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.
>>>>>
>>>>
>>>> Please start a new vote then for the master pom.
>>>>
>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> 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)
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>
>
Re: [DISCUSS] Apache Rave 0.21 Release Candidate
Posted by Raminder Singh <ra...@gmail.com>.
I moved to discussion thread.
You can checkout https://svn.apache.org/repos/asf/rave/rave-master-pom/trunk and add your info to pom. I am not sure if its required for the release. Just want to check with others before start the vote thread for master.
Thanks
Raminder
On Apr 5, 2013, at 4:23 PM, Erin Noe-Payne wrote:
> Sure. What do I need to do?
>
> On Fri, Apr 5, 2013 at 4:19 PM, Raminder Singh <ra...@gmail.com> wrote:
>> I just noticed, Erin is still not added to master pom as committer and PMC. Do we want to do that before 0.21 master release?
>>
>> Thanks
>> Raminder
>> On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
>>
>>> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
>>>
>>>> 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.
>>>>
>>>
>>> Please start a new vote then for the master pom.
>>>
>>>
>>>>
>>>>>
>>>>>
>>>>> 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)
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Erin Noe-Payne <er...@gmail.com>.
Sure. What do I need to do?
On Fri, Apr 5, 2013 at 4:19 PM, Raminder Singh <ra...@gmail.com> wrote:
> I just noticed, Erin is still not added to master pom as committer and PMC. Do we want to do that before 0.21 master release?
>
> Thanks
> Raminder
> On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
>
>> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
>>
>>> 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.
>>>
>>
>> Please start a new vote then for the master pom.
>>
>>
>>>
>>>>
>>>>
>>>> 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)
>>>>>>
>>>>>
>>>>
>>>
>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Raminder Singh <ra...@gmail.com>.
I just noticed, Erin is still not added to master pom as committer and PMC. Do we want to do that before 0.21 master release?
Thanks
Raminder
On Apr 5, 2013, at 10:02 AM, Jasha Joachimsthal wrote:
> On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
>
>> 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.
>>
>
> Please start a new vote then for the master pom.
>
>
>>
>>>
>>>
>>> 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)
>>>>>
>>>>
>>>
>>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Jasha Joachimsthal <ja...@apache.org>.
On 4 April 2013 22:32, Chris Geer <ch...@cxtsoftware.com> wrote:
> 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.
>
Please start a new vote then for the master pom.
>
> >
> >
> > 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)
> > > >
> > >
> >
>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Chris Geer <ch...@cxtsoftware.com>.
On Thu, Apr 4, 2013 at 1:30 PM, Matt Franklin <m....@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)
> > >
> >
>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Matt Franklin <m....@gmail.com>.
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.
On Thu, Apr 4, 2013 at 1:45 PM, Raminderjeet Singh <ra...@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)
> >
>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Raminderjeet Singh <ra...@indiana.edu>.
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 <ra...@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)
>
Re: [VOTE] Apache Rave 0.21 Release Candidate
Posted by Raminderjeet Singh <ra...@gmail.com>.
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 <ra...@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)
>