Re: [PROPOSAL] Prepare Beam 2.11.0 release

2019-02-14 Thread Ahmet Altay
Update: Post-commit tests were mostly green and I cut the branch earlier
today. There are 27 issues on the tagged for this release [1], I will start
triage them. I would appreciate if you can start moving non-release
blocking issues from this list.

[1] https://issues.apache.org/jira/projects/BEAM/versions/12344775

On Mon, Feb 11, 2019 at 1:26 PM Sam Rohde  wrote:

> Thanks Ahmet! The 2.11.0 release will also be using the revised release
> process from PR-7529  that I
> authored. Let me know if you have any questions or if I can help in any
> way. I would love feedback on how to improve on the modifications I made
> and the release process in general.
>
> On Fri, Feb 8, 2019 at 9:20 AM Scott Wegner  wrote:
>
>> +1, thanks Ahmet! Let us know if you need any help.
>>
>>
>> On Fri, Feb 8, 2019 at 8:09 AM Alan Myrvold  wrote:
>>
>>> Thanks for volunteering. Glad to see the schedule being kept.
>>>
>>> On Fri, Feb 8, 2019 at 5:58 AM Maximilian Michels 
>>> wrote:
>>>
 +1 We should keep up the release cycle even though we are a bit late
 with 2.10.0

 On 08.02.19 02:10, Andrew Pilloud wrote:
 > +1 let's keep things going. Thanks for volunteering!
 >
 > Andrew
 >
 > On Thu, Feb 7, 2019, 4:49 PM Kenneth Knowles >>> > > wrote:
 >
 > I think this is a good idea. Even though 2.10.0 is still making
 it's
 > way out, there's still 6 weeks of changes between the cut dates,
 > lots of value. It is good to keep the rhythm and follow the
 calendar.
 >
 > Kenn
 >
 > On Thu, Feb 7, 2019, 15:52 Ahmet Altay >>> >  wrote:
 >
 > Hi all,
 >
 > Beam 2.11 release branch cut date is 2/13 according to the
 > release calendar [1]. I would like to volunteer myself to do
 > this release. I intend to cut the branch on the planned 2/13
 date.
 >
 > If you have releasing blocking issues for 2.11 please mark
 their
 > "Fix Version" as 2.11.0. (I also created a 2.12.0 release in
 > JIRA in case you would like to move any non-blocking issues to
 > that version.)
 >
 > What do you think?
 >
 > Ahmet
 >
 > [1]
 >
 https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com=America%2FLos_Angeles
 >

>>>
>>
>> --
>>
>>
>>
>>
>> Got feedback? tinyurl.com/swegner-feedback
>>
>


Re: [PROPOSAL] Prepare Beam 2.11.0 release

2019-02-11 Thread Sam Rohde
Thanks Ahmet! The 2.11.0 release will also be using the revised release
process from PR-7529  that I
authored. Let me know if you have any questions or if I can help in any
way. I would love feedback on how to improve on the modifications I made
and the release process in general.

On Fri, Feb 8, 2019 at 9:20 AM Scott Wegner  wrote:

> +1, thanks Ahmet! Let us know if you need any help.
>
>
> On Fri, Feb 8, 2019 at 8:09 AM Alan Myrvold  wrote:
>
>> Thanks for volunteering. Glad to see the schedule being kept.
>>
>> On Fri, Feb 8, 2019 at 5:58 AM Maximilian Michels  wrote:
>>
>>> +1 We should keep up the release cycle even though we are a bit late
>>> with 2.10.0
>>>
>>> On 08.02.19 02:10, Andrew Pilloud wrote:
>>> > +1 let's keep things going. Thanks for volunteering!
>>> >
>>> > Andrew
>>> >
>>> > On Thu, Feb 7, 2019, 4:49 PM Kenneth Knowles >> > > wrote:
>>> >
>>> > I think this is a good idea. Even though 2.10.0 is still making
>>> it's
>>> > way out, there's still 6 weeks of changes between the cut dates,
>>> > lots of value. It is good to keep the rhythm and follow the
>>> calendar.
>>> >
>>> > Kenn
>>> >
>>> > On Thu, Feb 7, 2019, 15:52 Ahmet Altay >> >  wrote:
>>> >
>>> > Hi all,
>>> >
>>> > Beam 2.11 release branch cut date is 2/13 according to the
>>> > release calendar [1]. I would like to volunteer myself to do
>>> > this release. I intend to cut the branch on the planned 2/13
>>> date.
>>> >
>>> > If you have releasing blocking issues for 2.11 please mark
>>> their
>>> > "Fix Version" as 2.11.0. (I also created a 2.12.0 release in
>>> > JIRA in case you would like to move any non-blocking issues to
>>> > that version.)
>>> >
>>> > What do you think?
>>> >
>>> > Ahmet
>>> >
>>> > [1]
>>> >
>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com=America%2FLos_Angeles
>>> >
>>>
>>
>
> --
>
>
>
>
> Got feedback? tinyurl.com/swegner-feedback
>


Re: [PROPOSAL] Prepare Beam 2.11.0 release

2019-02-08 Thread Scott Wegner
+1, thanks Ahmet! Let us know if you need any help.


On Fri, Feb 8, 2019 at 8:09 AM Alan Myrvold  wrote:

> Thanks for volunteering. Glad to see the schedule being kept.
>
> On Fri, Feb 8, 2019 at 5:58 AM Maximilian Michels  wrote:
>
>> +1 We should keep up the release cycle even though we are a bit late
>> with 2.10.0
>>
>> On 08.02.19 02:10, Andrew Pilloud wrote:
>> > +1 let's keep things going. Thanks for volunteering!
>> >
>> > Andrew
>> >
>> > On Thu, Feb 7, 2019, 4:49 PM Kenneth Knowles > > > wrote:
>> >
>> > I think this is a good idea. Even though 2.10.0 is still making it's
>> > way out, there's still 6 weeks of changes between the cut dates,
>> > lots of value. It is good to keep the rhythm and follow the
>> calendar.
>> >
>> > Kenn
>> >
>> > On Thu, Feb 7, 2019, 15:52 Ahmet Altay > >  wrote:
>> >
>> > Hi all,
>> >
>> > Beam 2.11 release branch cut date is 2/13 according to the
>> > release calendar [1]. I would like to volunteer myself to do
>> > this release. I intend to cut the branch on the planned 2/13
>> date.
>> >
>> > If you have releasing blocking issues for 2.11 please mark their
>> > "Fix Version" as 2.11.0. (I also created a 2.12.0 release in
>> > JIRA in case you would like to move any non-blocking issues to
>> > that version.)
>> >
>> > What do you think?
>> >
>> > Ahmet
>> >
>> > [1]
>> >
>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com=America%2FLos_Angeles
>> >
>>
>

-- 




Got feedback? tinyurl.com/swegner-feedback


Re: [PROPOSAL] Prepare Beam 2.11.0 release

2019-02-08 Thread Alan Myrvold
Thanks for volunteering. Glad to see the schedule being kept.

On Fri, Feb 8, 2019 at 5:58 AM Maximilian Michels  wrote:

> +1 We should keep up the release cycle even though we are a bit late
> with 2.10.0
>
> On 08.02.19 02:10, Andrew Pilloud wrote:
> > +1 let's keep things going. Thanks for volunteering!
> >
> > Andrew
> >
> > On Thu, Feb 7, 2019, 4:49 PM Kenneth Knowles  > > wrote:
> >
> > I think this is a good idea. Even though 2.10.0 is still making it's
> > way out, there's still 6 weeks of changes between the cut dates,
> > lots of value. It is good to keep the rhythm and follow the calendar.
> >
> > Kenn
> >
> > On Thu, Feb 7, 2019, 15:52 Ahmet Altay  >  wrote:
> >
> > Hi all,
> >
> > Beam 2.11 release branch cut date is 2/13 according to the
> > release calendar [1]. I would like to volunteer myself to do
> > this release. I intend to cut the branch on the planned 2/13
> date.
> >
> > If you have releasing blocking issues for 2.11 please mark their
> > "Fix Version" as 2.11.0. (I also created a 2.12.0 release in
> > JIRA in case you would like to move any non-blocking issues to
> > that version.)
> >
> > What do you think?
> >
> > Ahmet
> >
> > [1]
> >
> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com=America%2FLos_Angeles
> >
>


Re: [PROPOSAL] Prepare Beam 2.11.0 release

2019-02-08 Thread Maximilian Michels
+1 We should keep up the release cycle even though we are a bit late 
with 2.10.0


On 08.02.19 02:10, Andrew Pilloud wrote:

+1 let's keep things going. Thanks for volunteering!

Andrew

On Thu, Feb 7, 2019, 4:49 PM Kenneth Knowles > wrote:


I think this is a good idea. Even though 2.10.0 is still making it's
way out, there's still 6 weeks of changes between the cut dates,
lots of value. It is good to keep the rhythm and follow the calendar.

Kenn

On Thu, Feb 7, 2019, 15:52 Ahmet Altay mailto:al...@google.com> wrote:

Hi all,

Beam 2.11 release branch cut date is 2/13 according to the
release calendar [1]. I would like to volunteer myself to do
this release. I intend to cut the branch on the planned 2/13 date.

If you have releasing blocking issues for 2.11 please mark their
"Fix Version" as 2.11.0. (I also created a 2.12.0 release in
JIRA in case you would like to move any non-blocking issues to
that version.)

What do you think?

Ahmet

[1]

https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com=America%2FLos_Angeles



Re: [PROPOSAL] Prepare Beam 2.11.0 release

2019-02-07 Thread Andrew Pilloud
+1 let's keep things going. Thanks for volunteering!

Andrew

On Thu, Feb 7, 2019, 4:49 PM Kenneth Knowles  wrote:

> I think this is a good idea. Even though 2.10.0 is still making it's way
> out, there's still 6 weeks of changes between the cut dates, lots of value.
> It is good to keep the rhythm and follow the calendar.
>
> Kenn
>
> On Thu, Feb 7, 2019, 15:52 Ahmet Altay 
>> Hi all,
>>
>> Beam 2.11 release branch cut date is 2/13 according to the release
>> calendar [1]. I would like to volunteer myself to do this release. I intend
>> to cut the branch on the planned 2/13 date.
>>
>> If you have releasing blocking issues for 2.11 please mark their "Fix
>> Version" as 2.11.0. (I also created a 2.12.0 release in JIRA in case you
>> would like to move any non-blocking issues to that version.)
>>
>> What do you think?
>>
>> Ahmet
>>
>> [1]
>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com=America%2FLos_Angeles
>>
>


Re: [PROPOSAL] Prepare Beam 2.11.0 release

2019-02-07 Thread Kenneth Knowles
I think this is a good idea. Even though 2.10.0 is still making it's way
out, there's still 6 weeks of changes between the cut dates, lots of value.
It is good to keep the rhythm and follow the calendar.

Kenn

On Thu, Feb 7, 2019, 15:52 Ahmet Altay  Hi all,
>
> Beam 2.11 release branch cut date is 2/13 according to the release
> calendar [1]. I would like to volunteer myself to do this release. I intend
> to cut the branch on the planned 2/13 date.
>
> If you have releasing blocking issues for 2.11 please mark their "Fix
> Version" as 2.11.0. (I also created a 2.12.0 release in JIRA in case you
> would like to move any non-blocking issues to that version.)
>
> What do you think?
>
> Ahmet
>
> [1]
> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com=America%2FLos_Angeles
>