On Mar 27, 2012, at 10:31 PM, Arun C Murthy wrote:

> I'll do the needful after midnight tonight. It should take less than half-an-hour, and I'll send out the all clear after.
>

Done, all clear; I've also created jira revisions. Please let me know if you find any issues.

thanks,
Arun

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Hey Arun,

On Wed, Mar 28, 2012 at 12:28 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:

> Done, all clear; I've also created jira revisions. Please let me know if
> you find any issues.
>

Thanks a lot for making these changes. Two questions:

- Now that we've renamed branch-0.23 to branch-2, and since there is as yet
no branch-0.23.3, what should be done with JIRAs marked with the 0.23.3
version? Perhaps all of these should be updated to 2.0.0?

- We still have the JIRA version 0.24.0, which is presumably still
representative of trunk. Given that we will likely never release an 0.24.0,
should we rename this version in JIRA as well?

--
Aaron T. Myers
Software Engineer, Cloudera

On Mar 28, 2012, at 12:48 AM, Aaron T. Myers wrote:

> Hey Arun,
>
> On Wed, Mar 28, 2012 at 12:28 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:
>
>> Done, all clear; I've also created jira revisions. Please let me know if
>> you find any issues.
>>
>
> Thanks a lot for making these changes. Two questions:
>
> - Now that we've renamed branch-0.23 to branch-2, and since there is as yet
> no branch-0.23.3, what should be done with JIRAs marked with the 0.23.3
> version? Perhaps all of these should be updated to 2.0.0?
>

Yep, in the process of doing it.

> - We still have the JIRA version 0.24.0, which is presumably still
> representative of trunk. Given that we will likely never release an 0.24.0,
> should we rename this version in JIRA as well?

I've created a 3.0.0 version in jira too. I'll update all jiras to point to that instead of 0.24.0.

thanks,
Arun

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

>
>
> > - Now that we've renamed branch-0.23 to branch-2, and since there is as
> yet
> > no branch-0.23.3, what should be done with JIRAs marked with the 0.23.3
> > version? Perhaps all of these should be updated to 2.0.0?
> >
>
> Yep, in the process of doing it.
>
>
Mhhh, shouldn't we use 2.0.3  here? IMO it would help correlating to the
previous 0.23.x releases

Thxs.

Alejandro

On Wed, Mar 28, 2012 at 5:11 PM, Doug Cutting <[EMAIL PROTECTED]> wrote:

> On 03/28/2012 12:39 PM, Owen O'Malley wrote:
> > [ ... ] So the RM of the 2 branch needs to make the call of what
> > should be 2.1 vs 3.0.
>
> I thought these were community decisions, not RM decisions, no?
>

 What to release is the RM's decision and then voted on by the community.
We tried voting on which features to include and it led to no releases for
two years. I think our users are better served by having good usable
releases.

-- Owen

On Thu, Mar 29, 2012 at 8:00 AM, Owen O'Malley <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 28, 2012 at 5:11 PM, Doug Cutting <[EMAIL PROTECTED]> wrote:
>
>> On 03/28/2012 12:39 PM, Owen O'Malley wrote:
>> > [ ... ] So the RM of the 2 branch needs to make the call of what
>> > should be 2.1 vs 3.0.
>>
>> I thought these were community decisions, not RM decisions, no?
>>
>
>  What to release is the RM's decision and then voted on by the community.
> We tried voting on which features to include and it led to no releases for
> two years. I think our users are better served by having good usable
> releases.
>

Roy was pointing out that there is an RM for a given release, but
there is not a RM for a branch. The RM does not decide what goes into
branch-2, that's happening on a patch by patch basis, and the RM
decides what to release based on what branch they pick and what they
merge to it.  So far it has been working well. Kudos to Arun.

Thanks,
Eli