- Original Message -
From: "Graham Percival"
To: "Carl Sorensen"
Cc: "Phil Holmes" ;
Sent: Sunday, April 17, 2011 2:51 PM
Subject: Re: stable/2.14 and fixed_2_x_y
On Sun, Apr 17, 2011 at 07:12:18AM -0600, Carl Sorensen wrote:
On 4/17/11 5:27 AM, &quo
On Sun, Apr 17, 2011 at 07:12:18AM -0600, Carl Sorensen wrote:
> On 4/17/11 5:27 AM, "Graham Percival" wrote:
>
> > Given the existing difficulties with the bug squad, there's no way
> > that I can support asking them to play with git master.
>
> I think you misunderstood my comment. There are
On 4/17/11 5:27 AM, "Graham Percival" wrote:
> On Sun, Apr 17, 2011 at 05:15:00AM -0600, Carl Sorensen wrote:
>>
>
>> But it would be nice if the Bug Squad could verify any issues that are fixed
>> pre 2.13.61 so that the list of issues to verify is the backport candidates.
>
> Given the exist
On Sun, Apr 17, 2011 at 05:15:00AM -0600, Carl Sorensen wrote:
>
> On 4/17/11 2:33 AM, "Graham Percival" wrote:
>
> > Instead, I think we should mark something as "fixed" if the patch
> > is in git master, but add a "backport" label. You will remove
> > that label when you actually do backport
On 4/17/11 2:33 AM, "Graham Percival" wrote:
> On Sat, Apr 16, 2011 at 12:01:43PM -0600, Carl Sorensen wrote:
>> On 4/16/11 5:02 AM, "Graham Percival" wrote:
>>
>>> If you fix something in the issue tracker, mark it fixed_2_15_0.
>>> Carl will add fixed_2_13_61, _62, _63, _64, etc., when he
On Sat, Apr 16, 2011 at 12:01:43PM -0600, Carl Sorensen wrote:
> On 4/16/11 5:02 AM, "Graham Percival" wrote:
>
> > If you fix something in the issue tracker, mark it fixed_2_15_0.
> > Carl will add fixed_2_13_61, _62, _63, _64, etc., when he
> > cherry-picks the patch to stable/2.14.
>
> Also,
On 4/16/11 5:02 AM, "Graham Percival" wrote:
> stable/2.14 has been branched. Carl is the only person who should
> touch that branch, other than me making release announcements and
> updating the version number. All future 2.13.x releases will be
> made from stable/2.14.
>
> If you fix somethi
stable/2.14 has been branched. Carl is the only person who should
touch that branch, other than me making release announcements and
updating the version number. All future 2.13.x releases will be
made from stable/2.14.
If you fix something in the issue tracker, mark it fixed_2_15_0.
Carl will ad
