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]

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

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

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

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

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

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