Matt Foley
2013-03-11, 03:38
Karthik Kambatla
2013-03-11, 16:01
Steve Loughran
2013-03-11, 16:57
Colin McCabe
2013-03-11, 18:52
Luke Lu
2013-03-11, 21:21
Thomas Graves
2013-03-13, 16:24
Thomas Graves
2013-03-13, 16:31
Steve Loughran
2013-03-14, 09:52
Robert Evans
2013-03-15, 16:12
Robert Evans
2013-03-15, 16:23
Karthik Kambatla
2013-03-15, 18:49
Harsh J
2013-03-17, 00:01
Harsh J
2013-03-17, 00:02
Tsuyoshi OZAWA
2013-03-18, 06:05
Daryn Sharp
2013-03-18, 13:10
Uma Maheswara Rao G
2013-03-18, 13:12
Matt Foley
2013-03-20, 16:40
Thomas Graves
2013-03-21, 15:25
Thomas Graves
2013-04-11, 13:05
-
[VOTE] Plan to create release candidate Monday 3/18Matt Foley 2013-03-11, 03:38
Hi all,
I have created branch-1.2 from branch-1, and propose to cut the first
release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
soon thereafter as I can achieve a stable build.
Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release
notes are available at .../branch-1.2/src/docs/releasenotes.html in the
sources.
Any non-destabilizing patches committed to branch-1.2 during the coming
week (and of course also committed to branch-1) will be included in the RC.
However, at this point I request that any big new developments not yet in
branch-1.2 be targeted for 1.3.
Release plans have to be voted on too, so please vote '+1' to approve this
plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
Thanks,
--Matt
(release manager)
I have created branch-1.2 from branch-1, and propose to cut the first
release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
soon thereafter as I can achieve a stable build.
Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release
notes are available at .../branch-1.2/src/docs/releasenotes.html in the
sources.
Any non-destabilizing patches committed to branch-1.2 during the coming
week (and of course also committed to branch-1) will be included in the RC.
However, at this point I request that any big new developments not yet in
branch-1.2 be targeted for 1.3.
Release plans have to be voted on too, so please vote '+1' to approve this
plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
Thanks,
--Matt
(release manager)
-
Re: [VOTE] Plan to create release candidate Monday 3/18Karthik Kambatla 2013-03-11, 16:01
+1 (non-binding)
On Sun, Mar 10, 2013 at 8:38 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Hi all,
> I have created branch-1.2 from branch-1, and propose to cut the first
> release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> soon thereafter as I can achieve a stable build.
>
> Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release
> notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> sources.
>
> Any non-destabilizing patches committed to branch-1.2 during the coming
> week (and of course also committed to branch-1) will be included in the RC.
> However, at this point I request that any big new developments not yet in
> branch-1.2 be targeted for 1.3.
>
> Release plans have to be voted on too, so please vote '+1' to approve this
> plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
>
> Thanks,
> --Matt
> (release manager)
>
On Sun, Mar 10, 2013 at 8:38 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Hi all,
> I have created branch-1.2 from branch-1, and propose to cut the first
> release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> soon thereafter as I can achieve a stable build.
>
> Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release
> notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> sources.
>
> Any non-destabilizing patches committed to branch-1.2 during the coming
> week (and of course also committed to branch-1) will be included in the RC.
> However, at this point I request that any big new developments not yet in
> branch-1.2 be targeted for 1.3.
>
> Release plans have to be voted on too, so please vote '+1' to approve this
> plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
>
> Thanks,
> --Matt
> (release manager)
>
-
Re: [VOTE] Plan to create release candidate Monday 3/18Steve Loughran 2013-03-11, 16:57
On 11 March 2013 03:38, Matt Foley <[EMAIL PROTECTED]> wrote:
> Hi all,
> I have created branch-1.2 from branch-1, and propose to cut the first
> release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> soon thereafter as I can achieve a stable build.
>
> Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release
> notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> sources.
>
> Any non-destabilizing patches committed to branch-1.2 during the coming
> week (and of course also committed to branch-1) will be included in the RC.
> However, at this point I request that any big new developments not yet in
> branch-1.2 be targeted for 1.3.
>
> Release plans have to be voted on too, so please vote '+1' to approve this
> plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
>
+1
> Hi all,
> I have created branch-1.2 from branch-1, and propose to cut the first
> release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> soon thereafter as I can achieve a stable build.
>
> Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release
> notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> sources.
>
> Any non-destabilizing patches committed to branch-1.2 during the coming
> week (and of course also committed to branch-1) will be included in the RC.
> However, at this point I request that any big new developments not yet in
> branch-1.2 be targeted for 1.3.
>
> Release plans have to be voted on too, so please vote '+1' to approve this
> plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
>
+1
-
Re: [VOTE] Plan to create release candidate Monday 3/18Colin McCabe 2013-03-11, 18:52
+1 (non-binding)
best,
Colin
On Sun, Mar 10, 2013 at 8:38 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Hi all,
> I have created branch-1.2 from branch-1, and propose to cut the first
> release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> soon thereafter as I can achieve a stable build.
>
> Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release
> notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> sources.
>
> Any non-destabilizing patches committed to branch-1.2 during the coming
> week (and of course also committed to branch-1) will be included in the RC.
> However, at this point I request that any big new developments not yet in
> branch-1.2 be targeted for 1.3.
>
> Release plans have to be voted on too, so please vote '+1' to approve this
> plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
>
> Thanks,
> --Matt
> (release manager)
>
best,
Colin
On Sun, Mar 10, 2013 at 8:38 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
> Hi all,
> I have created branch-1.2 from branch-1, and propose to cut the first
> release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> soon thereafter as I can achieve a stable build.
>
> Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft release
> notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> sources.
>
> Any non-destabilizing patches committed to branch-1.2 during the coming
> week (and of course also committed to branch-1) will be included in the RC.
> However, at this point I request that any big new developments not yet in
> branch-1.2 be targeted for 1.3.
>
> Release plans have to be voted on too, so please vote '+1' to approve this
> plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
>
> Thanks,
> --Matt
> (release manager)
>
-
Re: [VOTE] Plan to create release candidate Monday 3/18Luke Lu 2013-03-11, 21:21
+1.
On Mon, Mar 11, 2013 at 11:52 AM, Colin McCabe <[EMAIL PROTECTED]>wrote:
> +1 (non-binding)
>
> best,
> Colin
>
>
> On Sun, Mar 10, 2013 at 8:38 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
>
> > Hi all,
> > I have created branch-1.2 from branch-1, and propose to cut the first
> > release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> > soon thereafter as I can achieve a stable build.
> >
> > Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft
> release
> > notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> > sources.
> >
> > Any non-destabilizing patches committed to branch-1.2 during the coming
> > week (and of course also committed to branch-1) will be included in the
> RC.
> > However, at this point I request that any big new developments not yet
> in
> > branch-1.2 be targeted for 1.3.
> >
> > Release plans have to be voted on too, so please vote '+1' to approve
> this
> > plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
> >
> > Thanks,
> > --Matt
> > (release manager)
> >
>
On Mon, Mar 11, 2013 at 11:52 AM, Colin McCabe <[EMAIL PROTECTED]>wrote:
> +1 (non-binding)
>
> best,
> Colin
>
>
> On Sun, Mar 10, 2013 at 8:38 PM, Matt Foley <[EMAIL PROTECTED]> wrote:
>
> > Hi all,
> > I have created branch-1.2 from branch-1, and propose to cut the first
> > release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> > soon thereafter as I can achieve a stable build.
> >
> > Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft
> release
> > notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> > sources.
> >
> > Any non-destabilizing patches committed to branch-1.2 during the coming
> > week (and of course also committed to branch-1) will be included in the
> RC.
> > However, at this point I request that any big new developments not yet
> in
> > branch-1.2 be targeted for 1.3.
> >
> > Release plans have to be voted on too, so please vote '+1' to approve
> this
> > plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
> >
> > Thanks,
> > --Matt
> > (release manager)
> >
>
-
Re: [VOTE] Plan to create release candidate Monday 3/18Thomas Graves 2013-03-13, 16:24
+1.
Tom
On 3/10/13 10:38 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:
>Hi all,
>I have created branch-1.2 from branch-1, and propose to cut the first
>release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
>soon thereafter as I can achieve a stable build.
>
>Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft
>release
>notes are available at .../branch-1.2/src/docs/releasenotes.html in the
>sources.
>
>Any non-destabilizing patches committed to branch-1.2 during the coming
>week (and of course also committed to branch-1) will be included in the
>RC.
> However, at this point I request that any big new developments not yet in
>branch-1.2 be targeted for 1.3.
>
>Release plans have to be voted on too, so please vote '+1' to approve this
>plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
>
>Thanks,
>--Matt
>(release manager)
Tom
On 3/10/13 10:38 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:
>Hi all,
>I have created branch-1.2 from branch-1, and propose to cut the first
>release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
>soon thereafter as I can achieve a stable build.
>
>Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft
>release
>notes are available at .../branch-1.2/src/docs/releasenotes.html in the
>sources.
>
>Any non-destabilizing patches committed to branch-1.2 during the coming
>week (and of course also committed to branch-1) will be included in the
>RC.
> However, at this point I request that any big new developments not yet in
>branch-1.2 be targeted for 1.3.
>
>Release plans have to be voted on too, so please vote '+1' to approve this
>plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
>
>Thanks,
>--Matt
>(release manager)
-
[VOTE] Plan to create release candidate for 0.23.7Thomas Graves 2013-03-13, 16:31
Hello all,
I think enough critical bug fixes have went in to branch-0.23 that warrant another release. I plan on creating a 0.23.7 release by the end March.
Please vote '+1' to approve this plan. Voting will close on Wednesday 3/20 at 10:00am PDT.
Thanks,
Tom Graves
(release manager)
I think enough critical bug fixes have went in to branch-0.23 that warrant another release. I plan on creating a 0.23.7 release by the end March.
Please vote '+1' to approve this plan. Voting will close on Wednesday 3/20 at 10:00am PDT.
Thanks,
Tom Graves
(release manager)
-
Re: [VOTE] Plan to create release candidate for 0.23.7Steve Loughran 2013-03-14, 09:52
On 13 March 2013 16:31, Thomas Graves <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I think enough critical bug fixes have went in to branch-0.23 that warrant
> another release. I plan on creating a 0.23.7 release by the end March.
>
> Please vote '+1' to approve this plan. Voting will close on Wednesday
> 3/20 at 10:00am PDT.
>
>
> +1 non binding
> Hello all,
>
> I think enough critical bug fixes have went in to branch-0.23 that warrant
> another release. I plan on creating a 0.23.7 release by the end March.
>
> Please vote '+1' to approve this plan. Voting will close on Wednesday
> 3/20 at 10:00am PDT.
>
>
> +1 non binding
-
Re: [VOTE] Plan to create release candidate for 0.23.7Robert Evans 2013-03-15, 16:12
+1
On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>Hello all,
>
>I think enough critical bug fixes have went in to branch-0.23 that
>warrant another release. I plan on creating a 0.23.7 release by the end
>March.
>
>Please vote '+1' to approve this plan. Voting will close on Wednesday
>3/20 at 10:00am PDT.
>
>Thanks,
>Tom Graves
>(release manager)
On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>Hello all,
>
>I think enough critical bug fixes have went in to branch-0.23 that
>warrant another release. I plan on creating a 0.23.7 release by the end
>March.
>
>Please vote '+1' to approve this plan. Voting will close on Wednesday
>3/20 at 10:00am PDT.
>
>Thanks,
>Tom Graves
>(release manager)
-
Re: [VOTE] Plan to create release candidate Monday 3/18Robert Evans 2013-03-15, 16:23
+1
On 3/10/13 10:38 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:
>Hi all,
>I have created branch-1.2 from branch-1, and propose to cut the first
>release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
>soon thereafter as I can achieve a stable build.
>
>Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft
>release
>notes are available at .../branch-1.2/src/docs/releasenotes.html in the
>sources.
>
>Any non-destabilizing patches committed to branch-1.2 during the coming
>week (and of course also committed to branch-1) will be included in the
>RC.
> However, at this point I request that any big new developments not yet in
>branch-1.2 be targeted for 1.3.
>
>Release plans have to be voted on too, so please vote '+1' to approve this
>plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
>
>Thanks,
>--Matt
>(release manager)
On 3/10/13 10:38 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:
>Hi all,
>I have created branch-1.2 from branch-1, and propose to cut the first
>release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
>soon thereafter as I can achieve a stable build.
>
>Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft
>release
>notes are available at .../branch-1.2/src/docs/releasenotes.html in the
>sources.
>
>Any non-destabilizing patches committed to branch-1.2 during the coming
>week (and of course also committed to branch-1) will be included in the
>RC.
> However, at this point I request that any big new developments not yet in
>branch-1.2 be targeted for 1.3.
>
>Release plans have to be voted on too, so please vote '+1' to approve this
>plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
>
>Thanks,
>--Matt
>(release manager)
-
Re: [VOTE] Plan to create release candidate for 0.23.7Karthik Kambatla 2013-03-15, 18:49
+1 (non-binding)
On Fri, Mar 15, 2013 at 9:12 AM, Robert Evans <[EMAIL PROTECTED]> wrote:
> +1
>
> On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>
> >Hello all,
> >
> >I think enough critical bug fixes have went in to branch-0.23 that
> >warrant another release. I plan on creating a 0.23.7 release by the end
> >March.
> >
> >Please vote '+1' to approve this plan. Voting will close on Wednesday
> >3/20 at 10:00am PDT.
> >
> >Thanks,
> >Tom Graves
> >(release manager)
>
>
On Fri, Mar 15, 2013 at 9:12 AM, Robert Evans <[EMAIL PROTECTED]> wrote:
> +1
>
> On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>
> >Hello all,
> >
> >I think enough critical bug fixes have went in to branch-0.23 that
> >warrant another release. I plan on creating a 0.23.7 release by the end
> >March.
> >
> >Please vote '+1' to approve this plan. Voting will close on Wednesday
> >3/20 at 10:00am PDT.
> >
> >Thanks,
> >Tom Graves
> >(release manager)
>
>
-
Re: [VOTE] Plan to create release candidate for 0.23.7Harsh J 2013-03-17, 00:01
+1
On Sat, Mar 16, 2013 at 12:19 AM, Karthik Kambatla <[EMAIL PROTECTED]>wrote:
> +1 (non-binding)
>
> On Fri, Mar 15, 2013 at 9:12 AM, Robert Evans <[EMAIL PROTECTED]> wrote:
>
> > +1
> >
> > On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
> >
> > >Hello all,
> > >
> > >I think enough critical bug fixes have went in to branch-0.23 that
> > >warrant another release. I plan on creating a 0.23.7 release by the end
> > >March.
> > >
> > >Please vote '+1' to approve this plan. Voting will close on Wednesday
> > >3/20 at 10:00am PDT.
> > >
> > >Thanks,
> > >Tom Graves
> > >(release manager)
> >
> >
>
--
Harsh J
On Sat, Mar 16, 2013 at 12:19 AM, Karthik Kambatla <[EMAIL PROTECTED]>wrote:
> +1 (non-binding)
>
> On Fri, Mar 15, 2013 at 9:12 AM, Robert Evans <[EMAIL PROTECTED]> wrote:
>
> > +1
> >
> > On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
> >
> > >Hello all,
> > >
> > >I think enough critical bug fixes have went in to branch-0.23 that
> > >warrant another release. I plan on creating a 0.23.7 release by the end
> > >March.
> > >
> > >Please vote '+1' to approve this plan. Voting will close on Wednesday
> > >3/20 at 10:00am PDT.
> > >
> > >Thanks,
> > >Tom Graves
> > >(release manager)
> >
> >
>
--
Harsh J
-
Re: [VOTE] Plan to create release candidate Monday 3/18Harsh J 2013-03-17, 00:02
+1
On Fri, Mar 15, 2013 at 9:53 PM, Robert Evans <[EMAIL PROTECTED]> wrote:
> +1
>
> On 3/10/13 10:38 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:
>
> >Hi all,
> >I have created branch-1.2 from branch-1, and propose to cut the first
> >release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> >soon thereafter as I can achieve a stable build.
> >
> >Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft
> >release
> >notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> >sources.
> >
> >Any non-destabilizing patches committed to branch-1.2 during the coming
> >week (and of course also committed to branch-1) will be included in the
> >RC.
> > However, at this point I request that any big new developments not yet in
> >branch-1.2 be targeted for 1.3.
> >
> >Release plans have to be voted on too, so please vote '+1' to approve this
> >plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
> >
> >Thanks,
> >--Matt
> >(release manager)
>
>
--
Harsh J
On Fri, Mar 15, 2013 at 9:53 PM, Robert Evans <[EMAIL PROTECTED]> wrote:
> +1
>
> On 3/10/13 10:38 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:
>
> >Hi all,
> >I have created branch-1.2 from branch-1, and propose to cut the first
> >release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> >soon thereafter as I can achieve a stable build.
> >
> >Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft
> >release
> >notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> >sources.
> >
> >Any non-destabilizing patches committed to branch-1.2 during the coming
> >week (and of course also committed to branch-1) will be included in the
> >RC.
> > However, at this point I request that any big new developments not yet in
> >branch-1.2 be targeted for 1.3.
> >
> >Release plans have to be voted on too, so please vote '+1' to approve this
> >plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
> >
> >Thanks,
> >--Matt
> >(release manager)
>
>
--
Harsh J
-
Re: [VOTE] Plan to create release candidate for 0.23.7Tsuyoshi OZAWA 2013-03-18, 06:05
+1 (non-binding)
On Sun, Mar 17, 2013 at 9:01 AM, Harsh J <[EMAIL PROTECTED]> wrote:
> +1
>
>
> On Sat, Mar 16, 2013 at 12:19 AM, Karthik Kambatla <[EMAIL PROTECTED]>wrote:
>
>> +1 (non-binding)
>>
>> On Fri, Mar 15, 2013 at 9:12 AM, Robert Evans <[EMAIL PROTECTED]> wrote:
>>
>> > +1
>> >
>> > On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>> >
>> > >Hello all,
>> > >
>> > >I think enough critical bug fixes have went in to branch-0.23 that
>> > >warrant another release. I plan on creating a 0.23.7 release by the end
>> > >March.
>> > >
>> > >Please vote '+1' to approve this plan. Voting will close on Wednesday
>> > >3/20 at 10:00am PDT.
>> > >
>> > >Thanks,
>> > >Tom Graves
>> > >(release manager)
>> >
>> >
>>
>
>
>
> --
> Harsh J
--
- Tsuyoshi
On Sun, Mar 17, 2013 at 9:01 AM, Harsh J <[EMAIL PROTECTED]> wrote:
> +1
>
>
> On Sat, Mar 16, 2013 at 12:19 AM, Karthik Kambatla <[EMAIL PROTECTED]>wrote:
>
>> +1 (non-binding)
>>
>> On Fri, Mar 15, 2013 at 9:12 AM, Robert Evans <[EMAIL PROTECTED]> wrote:
>>
>> > +1
>> >
>> > On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>> >
>> > >Hello all,
>> > >
>> > >I think enough critical bug fixes have went in to branch-0.23 that
>> > >warrant another release. I plan on creating a 0.23.7 release by the end
>> > >March.
>> > >
>> > >Please vote '+1' to approve this plan. Voting will close on Wednesday
>> > >3/20 at 10:00am PDT.
>> > >
>> > >Thanks,
>> > >Tom Graves
>> > >(release manager)
>> >
>> >
>>
>
>
>
> --
> Harsh J
--
- Tsuyoshi
-
Re: [VOTE] Plan to create release candidate for 0.23.7Daryn Sharp 2013-03-18, 13:10
+1 (non-binding)
On Mar 18, 2013, at 1:05 AM, Tsuyoshi OZAWA wrote:
> +1 (non-binding)
>
> On Sun, Mar 17, 2013 at 9:01 AM, Harsh J <[EMAIL PROTECTED]> wrote:
>> +1
>>
>>
>> On Sat, Mar 16, 2013 at 12:19 AM, Karthik Kambatla <[EMAIL PROTECTED]>wrote:
>>
>>> +1 (non-binding)
>>>
>>> On Fri, Mar 15, 2013 at 9:12 AM, Robert Evans <[EMAIL PROTECTED]> wrote:
>>>
>>>> +1
>>>>
>>>> On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> Hello all,
>>>>>
>>>>> I think enough critical bug fixes have went in to branch-0.23 that
>>>>> warrant another release. I plan on creating a 0.23.7 release by the end
>>>>> March.
>>>>>
>>>>> Please vote '+1' to approve this plan. Voting will close on Wednesday
>>>>> 3/20 at 10:00am PDT.
>>>>>
>>>>> Thanks,
>>>>> Tom Graves
>>>>> (release manager)
>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Harsh J
>
>
>
> --
> - Tsuyoshi
On Mar 18, 2013, at 1:05 AM, Tsuyoshi OZAWA wrote:
> +1 (non-binding)
>
> On Sun, Mar 17, 2013 at 9:01 AM, Harsh J <[EMAIL PROTECTED]> wrote:
>> +1
>>
>>
>> On Sat, Mar 16, 2013 at 12:19 AM, Karthik Kambatla <[EMAIL PROTECTED]>wrote:
>>
>>> +1 (non-binding)
>>>
>>> On Fri, Mar 15, 2013 at 9:12 AM, Robert Evans <[EMAIL PROTECTED]> wrote:
>>>
>>>> +1
>>>>
>>>> On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> Hello all,
>>>>>
>>>>> I think enough critical bug fixes have went in to branch-0.23 that
>>>>> warrant another release. I plan on creating a 0.23.7 release by the end
>>>>> March.
>>>>>
>>>>> Please vote '+1' to approve this plan. Voting will close on Wednesday
>>>>> 3/20 at 10:00am PDT.
>>>>>
>>>>> Thanks,
>>>>> Tom Graves
>>>>> (release manager)
>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Harsh J
>
>
>
> --
> - Tsuyoshi
-
RE: [VOTE] Plan to create release candidate for 0.23.7Uma Maheswara Rao G 2013-03-18, 13:12
+1
________________________________________
From: Thomas Graves [[EMAIL PROTECTED]]
Sent: Wednesday, March 13, 2013 10:01 PM
To: [EMAIL PROTECTED]
Subject: [VOTE] Plan to create release candidate for 0.23.7
Hello all,
I think enough critical bug fixes have went in to branch-0.23 that warrant another release. I plan on creating a 0.23.7 release by the end March.
Please vote '+1' to approve this plan. Voting will close on Wednesday 3/20 at 10:00am PDT.
Thanks,
Tom Graves
(release manager)
________________________________________
From: Thomas Graves [[EMAIL PROTECTED]]
Sent: Wednesday, March 13, 2013 10:01 PM
To: [EMAIL PROTECTED]
Subject: [VOTE] Plan to create release candidate for 0.23.7
Hello all,
I think enough critical bug fixes have went in to branch-0.23 that warrant another release. I plan on creating a 0.23.7 release by the end March.
Please vote '+1' to approve this plan. Voting will close on Wednesday 3/20 at 10:00am PDT.
Thanks,
Tom Graves
(release manager)
-
Re: [VOTE] Plan to create release candidate Monday 3/18Matt Foley 2013-03-20, 16:40
Thank you all for voting. With six binding +1, two non-binding +1, and no
0 or -1, the release plan passes.
I am in process of making the first 1.2.0-RC build, and will put it up as
soon as possible.
Best regards,
--Matt
On Sat, Mar 16, 2013 at 5:02 PM, Harsh J <[EMAIL PROTECTED]> wrote:
> +1
>
>
> On Fri, Mar 15, 2013 at 9:53 PM, Robert Evans <[EMAIL PROTECTED]> wrote:
>
> > +1
> >
> > On 3/10/13 10:38 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:
> >
> > >Hi all,
> > >I have created branch-1.2 from branch-1, and propose to cut the first
> > >release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> > >soon thereafter as I can achieve a stable build.
> > >
> > >Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft
> > >release
> > >notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> > >sources.
> > >
> > >Any non-destabilizing patches committed to branch-1.2 during the coming
> > >week (and of course also committed to branch-1) will be included in the
> > >RC.
> > > However, at this point I request that any big new developments not yet
> in
> > >branch-1.2 be targeted for 1.3.
> > >
> > >Release plans have to be voted on too, so please vote '+1' to approve
> this
> > >plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
> > >
> > >Thanks,
> > >--Matt
> > >(release manager)
> >
> >
>
>
> --
> Harsh J
>
0 or -1, the release plan passes.
I am in process of making the first 1.2.0-RC build, and will put it up as
soon as possible.
Best regards,
--Matt
On Sat, Mar 16, 2013 at 5:02 PM, Harsh J <[EMAIL PROTECTED]> wrote:
> +1
>
>
> On Fri, Mar 15, 2013 at 9:53 PM, Robert Evans <[EMAIL PROTECTED]> wrote:
>
> > +1
> >
> > On 3/10/13 10:38 PM, "Matt Foley" <[EMAIL PROTECTED]> wrote:
> >
> > >Hi all,
> > >I have created branch-1.2 from branch-1, and propose to cut the first
> > >release candidate for 1.2.0 on Monday 3/18 (a week from tomorrow), or as
> > >soon thereafter as I can achieve a stable build.
> > >
> > >Between 1.1.2 and the current 1.2.0, there are 176 patches!! Draft
> > >release
> > >notes are available at .../branch-1.2/src/docs/releasenotes.html in the
> > >sources.
> > >
> > >Any non-destabilizing patches committed to branch-1.2 during the coming
> > >week (and of course also committed to branch-1) will be included in the
> > >RC.
> > > However, at this point I request that any big new developments not yet
> in
> > >branch-1.2 be targeted for 1.3.
> > >
> > >Release plans have to be voted on too, so please vote '+1' to approve
> this
> > >plan. Voting will close on Sunday 3/17 at 8:30pm PDT.
> > >
> > >Thanks,
> > >--Matt
> > >(release manager)
> >
> >
>
>
> --
> Harsh J
>
-
Re: [VOTE] Plan to create release candidate for 0.23.7Thomas Graves 2013-03-21, 15:25
Thanks everyone for voting. With 4 binding +1, 4 non-binding +1, and no -1
the release plan passes. I will make a release here soon, tentatively
planned for next week once the blockers are all committed.
Tom
On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>Hello all,
>
>I think enough critical bug fixes have went in to branch-0.23 that
>warrant another release. I plan on creating a 0.23.7 release by the end
>March.
>
>Please vote '+1' to approve this plan. Voting will close on Wednesday
>3/20 at 10:00am PDT.
>
>Thanks,
>Tom Graves
>(release manager)
the release plan passes. I will make a release here soon, tentatively
planned for next week once the blockers are all committed.
Tom
On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>Hello all,
>
>I think enough critical bug fixes have went in to branch-0.23 that
>warrant another release. I plan on creating a 0.23.7 release by the end
>March.
>
>Please vote '+1' to approve this plan. Voting will close on Wednesday
>3/20 at 10:00am PDT.
>
>Thanks,
>Tom Graves
>(release manager)
-
Re: [VOTE] Plan to create release candidate for 0.23.7Thomas Graves 2013-04-11, 13:05
Sorry for the delay on this, I was waiting for a couple of blockers to be
resolved. I am planning on spinning this release today.
Tom
On 3/21/13 10:25 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>Thanks everyone for voting. With 4 binding +1, 4 non-binding +1, and no -1
>the release plan passes. I will make a release here soon, tentatively
>planned for next week once the blockers are all committed.
>
>Tom
>
>On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>
>>Hello all,
>>
>>I think enough critical bug fixes have went in to branch-0.23 that
>>warrant another release. I plan on creating a 0.23.7 release by the end
>>March.
>>
>>Please vote '+1' to approve this plan. Voting will close on Wednesday
>>3/20 at 10:00am PDT.
>>
>>Thanks,
>>Tom Graves
>>(release manager)
>
resolved. I am planning on spinning this release today.
Tom
On 3/21/13 10:25 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>Thanks everyone for voting. With 4 binding +1, 4 non-binding +1, and no -1
>the release plan passes. I will make a release here soon, tentatively
>planned for next week once the blockers are all committed.
>
>Tom
>
>On 3/13/13 11:31 AM, "Thomas Graves" <[EMAIL PROTECTED]> wrote:
>
>>Hello all,
>>
>>I think enough critical bug fixes have went in to branch-0.23 that
>>warrant another release. I plan on creating a 0.23.7 release by the end
>>March.
>>
>>Please vote '+1' to approve this plan. Voting will close on Wednesday
>>3/20 at 10:00am PDT.
>>
>>Thanks,
>>Tom Graves
>>(release manager)
>
