People tend to produce patches against the 0.7.1. Currently I think we are
urging double commits on trunk and 0.8 because the large code difference
makes auto merges too dangerous. However I don't think we are likely to do
a 0.7.2 release (0.8 is not too far out at this point). So I think we
should be advising people to giving any non-critical patches just against
0.8, right?

Thoughts?

-Jay

0.7.1 patch == patch to apply on branch 0.7.1 or trunk? I thought we would
be doing double-commits on trunk and 0.8 and not worry about release
branches for now. Also, 0.7.2 would be cut off trunk. (Both 0.7.1 and 0.7
were cut off trunk.)

Joel
On Wed, Jul 18, 2012 at 10:19 AM, Jay Kreps <[EMAIL PROTECTED]> wrote:

> People tend to produce patches against the 0.7.1. Currently I think we are
> urging double commits on trunk and 0.8 because the large code difference
> makes auto merges too dangerous. However I don't think we are likely to do
> a 0.7.2 release (0.8 is not too far out at this point). So I think we
> should be advising people to giving any non-critical patches just against
> 0.8, right?
>
> Thoughts?
>
> -Jay
>

I was thinking we would have a 0.7.2 release if there are patches in trunk
that folks want to use, why not release them and make it available for
them?  I don't mind doing releases ... double commits make this manageable

0.7.X off trunk, yup

On Wed, Jul 18, 2012 at 1:27 PM, Joel Koshy <[EMAIL PROTECTED]> wrote:

> 0.7.1 patch == patch to apply on branch 0.7.1 or trunk? I thought we would
> be doing double-commits on trunk and 0.8 and not worry about release
> branches for now. Also, 0.7.2 would be cut off trunk. (Both 0.7.1 and 0.7
> were cut off trunk.)
>
> Joel
>
>
> On Wed, Jul 18, 2012 at 10:19 AM, Jay Kreps <[EMAIL PROTECTED]> wrote:
>
> > People tend to produce patches against the 0.7.1. Currently I think we
> are
> > urging double commits on trunk and 0.8 because the large code difference
> > makes auto merges too dangerous. However I don't think we are likely to
> do
> > a 0.7.2 release (0.8 is not too far out at this point). So I think we
> > should be advising people to giving any non-critical patches just against
> > 0.8, right?
> >
> > Thoughts?
> >
> > -Jay
> >
>

--

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

I added a 0.7.2 release in JIRA for you (Joe, do you have the bits
flipped to be able to do this?)

On 07/18/2012 02:05 PM, Joe Stein wrote:
> I was thinking we would have a 0.7.2 release if there are patches in trunk
> that folks want to use, why not release them and make it available for
> them?  I don't mind doing releases ... double commits make this manageable
>
> 0.7.X off trunk, yup
>
> On Wed, Jul 18, 2012 at 1:27 PM, Joel Koshy <[EMAIL PROTECTED]> wrote:
>
>> 0.7.1 patch == patch to apply on branch 0.7.1 or trunk? I thought we would
>> be doing double-commits on trunk and 0.8 and not worry about release
>> branches for now. Also, 0.7.2 would be cut off trunk. (Both 0.7.1 and 0.7
>> were cut off trunk.)
>>
>> Joel
>>
>>
>> On Wed, Jul 18, 2012 at 10:19 AM, Jay Kreps <[EMAIL PROTECTED]> wrote:
>>
>>> People tend to produce patches against the 0.7.1. Currently I think we
>> are
>>> urging double commits on trunk and 0.8 because the large code difference
>>> makes auto merges too dangerous. However I don't think we are likely to
>> do
>>> a 0.7.2 release (0.8 is not too far out at this point). So I think we
>>> should be advising people to giving any non-critical patches just against
>>> 0.8, right?
>>>
>>> Thoughts?
>>>
>>> -Jay
>>>
>>
>
>
>

I think it might be useful for the community to have a couple more releases
for 0.7.*, at least until 0.8 is fully stable.

Thanks,
Neha

On Wed, Jul 18, 2012 at 1:03 PM, Chris Burroughs
<[EMAIL PROTECTED]>wrote:

> I added a 0.7.2 release in JIRA for you (Joe, do you have the bits
> flipped to be able to do this?)
>
> On 07/18/2012 02:05 PM, Joe Stein wrote:
> > I was thinking we would have a 0.7.2 release if there are patches in
> trunk
> > that folks want to use, why not release them and make it available for
> > them?  I don't mind doing releases ... double commits make this
> manageable
> >
> > 0.7.X off trunk, yup
> >
> > On Wed, Jul 18, 2012 at 1:27 PM, Joel Koshy <[EMAIL PROTECTED]> wrote:
> >
> >> 0.7.1 patch == patch to apply on branch 0.7.1 or trunk? I thought we
> would
> >> be doing double-commits on trunk and 0.8 and not worry about release
> >> branches for now. Also, 0.7.2 would be cut off trunk. (Both 0.7.1 and
> 0.7
> >> were cut off trunk.)
> >>
> >> Joel
> >>
> >>
> >> On Wed, Jul 18, 2012 at 10:19 AM, Jay Kreps <[EMAIL PROTECTED]>
> wrote:
> >>
> >>> People tend to produce patches against the 0.7.1. Currently I think we
> >> are
> >>> urging double commits on trunk and 0.8 because the large code
> difference
> >>> makes auto merges too dangerous. However I don't think we are likely to
> >> do
> >>> a 0.7.2 release (0.8 is not too far out at this point). So I think we
> >>> should be advising people to giving any non-critical patches just
> against
> >>> 0.8, right?
> >>>
> >>> Thoughts?
> >>>
> >>> -Jay
> >>>
> >>
> >
> >
> >
>
>

Cool, then I guess we can go case by case on double-checkins to trunk and
0.8.

-Jay

On Wed, Jul 18, 2012 at 1:13 PM, Neha Narkhede <[EMAIL PROTECTED]>wrote:

> I think it might be useful for the community to have a couple more releases
> for 0.7.*, at least until 0.8 is fully stable.
>
> Thanks,
> Neha
>
> On Wed, Jul 18, 2012 at 1:03 PM, Chris Burroughs
> <[EMAIL PROTECTED]>wrote:
>
> > I added a 0.7.2 release in JIRA for you (Joe, do you have the bits
> > flipped to be able to do this?)
> >
> > On 07/18/2012 02:05 PM, Joe Stein wrote:
> > > I was thinking we would have a 0.7.2 release if there are patches in
> > trunk
> > > that folks want to use, why not release them and make it available for
> > > them?  I don't mind doing releases ... double commits make this
> > manageable
> > >
> > > 0.7.X off trunk, yup
> > >
> > > On Wed, Jul 18, 2012 at 1:27 PM, Joel Koshy <[EMAIL PROTECTED]>
> wrote:
> > >
> > >> 0.7.1 patch == patch to apply on branch 0.7.1 or trunk? I thought we
> > would
> > >> be doing double-commits on trunk and 0.8 and not worry about release
> > >> branches for now. Also, 0.7.2 would be cut off trunk. (Both 0.7.1 and
> > 0.7
> > >> were cut off trunk.)
> > >>
> > >> Joel
> > >>
> > >>
> > >> On Wed, Jul 18, 2012 at 10:19 AM, Jay Kreps <[EMAIL PROTECTED]>
> > wrote:
> > >>
> > >>> People tend to produce patches against the 0.7.1. Currently I think
> we
> > >> are
> > >>> urging double commits on trunk and 0.8 because the large code
> > difference
> > >>> makes auto merges too dangerous. However I don't think we are likely
> to
> > >> do
> > >>> a 0.7.2 release (0.8 is not too far out at this point). So I think we
> > >>> should be advising people to giving any non-critical patches just
> > against
> > >>> 0.8, right?
> > >>>
> > >>> Thoughts?
> > >>>
> > >>> -Jay
> > >>>
> > >>
> > >
> > >
> > >
> >
> >
>

Would management of these concurrent branches be significantly easier if
we switched from svn to git?

On 07/18/2012 07:01 PM, Jay Kreps wrote:
> Cool, then I guess we can go case by case on double-checkins to trunk and
> 0.8.
>
> -Jay
>
> On Wed, Jul 18, 2012 at 1:13 PM, Neha Narkhede <[EMAIL PROTECTED]>wrote:
>
>> I think it might be useful for the community to have a couple more releases
>> for 0.7.*, at least until 0.8 is fully stable.
>>
>> Thanks,
>> Neha
>>
>> On Wed, Jul 18, 2012 at 1:03 PM, Chris Burroughs
>> <[EMAIL PROTECTED]>wrote:
>>
>>> I added a 0.7.2 release in JIRA for you (Joe, do you have the bits
>>> flipped to be able to do this?)
>>>
>>> On 07/18/2012 02:05 PM, Joe Stein wrote:
>>>> I was thinking we would have a 0.7.2 release if there are patches in
>>> trunk
>>>> that folks want to use, why not release them and make it available for
>>>> them?  I don't mind doing releases ... double commits make this
>>> manageable
>>>>
>>>> 0.7.X off trunk, yup
>>>>
>>>> On Wed, Jul 18, 2012 at 1:27 PM, Joel Koshy <[EMAIL PROTECTED]>
>> wrote:
>>>>
>>>>> 0.7.1 patch == patch to apply on branch 0.7.1 or trunk? I thought we
>>> would
>>>>> be doing double-commits on trunk and 0.8 and not worry about release
>>>>> branches for now. Also, 0.7.2 would be cut off trunk. (Both 0.7.1 and
>>> 0.7
>>>>> were cut off trunk.)
>>>>>
>>>>> Joel
>>>>>
>>>>>
>>>>> On Wed, Jul 18, 2012 at 10:19 AM, Jay Kreps <[EMAIL PROTECTED]>
>>> wrote:
>>>>>
>>>>>> People tend to produce patches against the 0.7.1. Currently I think
>> we
>>>>> are
>>>>>> urging double commits on trunk and 0.8 because the large code
>>> difference
>>>>>> makes auto merges too dangerous. However I don't think we are likely
>> to
>>>>> do
>>>>>> a 0.7.2 release (0.8 is not too far out at this point). So I think we
>>>>>> should be advising people to giving any non-critical patches just
>>> against
>>>>>> 0.8, right?
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> -Jay
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>

Yes it's an option if you ask with caveats about it not being as
polished as SVN support, users are expected to be extra helpful if
things break, etc.

Will start a new thread for further discussion.

On 07/26/2012 09:04 AM, Jay Kreps wrote:
> Yes. Also just patch management in general. I think most people are using the svn-git integration anyway.
>
> Anyone know the state of git support at apache? I heard other projects have switched over. Is that generally available?
>
> Sent from my iPhone
>
> On Jul 26, 2012, at 5:31 AM, Chris Burroughs <[EMAIL PROTECTED]> wrote:
>
>> Would management of these concurrent branches be significantly easier if
>> we switched from svn to git?
>>
>> On 07/18/2012 07:01 PM, Jay Kreps wrote:
>>> Cool, then I guess we can go case by case on double-checkins to trunk and
>>> 0.8.
>>>
>>> -Jay
>>>
>>> On Wed, Jul 18, 2012 at 1:13 PM, Neha Narkhede <[EMAIL PROTECTED]>wrote:
>>>
>>>> I think it might be useful for the community to have a couple more releases
>>>> for 0.7.*, at least until 0.8 is fully stable.
>>>>
>>>> Thanks,
>>>> Neha
>>>>
>>>> On Wed, Jul 18, 2012 at 1:03 PM, Chris Burroughs
>>>> <[EMAIL PROTECTED]>wrote:
>>>>
>>>>> I added a 0.7.2 release in JIRA for you (Joe, do you have the bits
>>>>> flipped to be able to do this?)
>>>>>
>>>>> On 07/18/2012 02:05 PM, Joe Stein wrote:
>>>>>> I was thinking we would have a 0.7.2 release if there are patches in
>>>>> trunk
>>>>>> that folks want to use, why not release them and make it available for
>>>>>> them?  I don't mind doing releases ... double commits make this
>>>>> manageable
>>>>>>
>>>>>> 0.7.X off trunk, yup
>>>>>>
>>>>>> On Wed, Jul 18, 2012 at 1:27 PM, Joel Koshy <[EMAIL PROTECTED]>
>>>> wrote:
>>>>>>
>>>>>>> 0.7.1 patch == patch to apply on branch 0.7.1 or trunk? I thought we
>>>>> would
>>>>>>> be doing double-commits on trunk and 0.8 and not worry about release
>>>>>>> branches for now. Also, 0.7.2 would be cut off trunk. (Both 0.7.1 and
>>>>> 0.7
>>>>>>> were cut off trunk.)
>>>>>>>
>>>>>>> Joel
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jul 18, 2012 at 10:19 AM, Jay Kreps <[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>>>
>>>>>>>> People tend to produce patches against the 0.7.1. Currently I think
>>>> we
>>>>>>> are
>>>>>>>> urging double commits on trunk and 0.8 because the large code
>>>>> difference
>>>>>>>> makes auto merges too dangerous. However I don't think we are likely
>>>> to
>>>>>>> do
>>>>>>>> a 0.7.2 release (0.8 is not too far out at this point). So I think we
>>>>>>>> should be advising people to giving any non-critical patches just
>>>>> against
>>>>>>>> 0.8, right?
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>>
>>>>>>>> -Jay
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>