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 <[email protected]> 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 < >> [email protected]> >>> 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 < >>> [email protected]> 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 <[email protected]> wrote: >>>>>>>> >>>>>>>>> On Thu, Apr 4, 2013 at 1:30 PM, Matt Franklin < >>> [email protected] >>>>>>>>>> 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 < >>> [email protected] >>>>>>>>>>> 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 < >>>>>>>>> [email protected] >>>>>>>>>>>> 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 >>
