Re: [PROPOSAL] Planning for next releases

2018-02-12 Thread Matteo Merli
Sure, can we also start early in creating the 1.22 branch? We have a lot of changes meant for 2.0 that are waiting to be merged after 1.22. On Thu, Feb 8, 2018 at 9:04 PM Jai Asher wrote: > Hi, > Rajan and I are planning to start the release process on Monday (12 > Feb). > Is everyone f

Re: [PROPOSAL] Planning for next releases

2018-02-08 Thread Jai Asher
Hi, Rajan and I are planning to start the release process on Monday (12 Feb). Is everyone fine with this? If yes then kindly get your PR merged by Monday. Regards, Jai On Sun, Jan 21, 2018 at 11:28 PM, Rajan Dhabalia wrote: > Hi, > > Yes, we can target 1.22.0-incubating release by revie

Re: [PROPOSAL] Planning for next releases

2018-01-24 Thread Sahaya Andrews
Can we create the branch at the end of this month? I would like to get C++ client encryption changes in. Will send out the PR in a day/two. Andrews. On Tue, Jan 23, 2018 at 10:21 PM, Masakazu Kitajo wrote: > I have one concern. We are now trying to format our code. If the code will > be formatte

Re: [PROPOSAL] Planning for next releases

2018-01-23 Thread Masakazu Kitajo
I have one concern. We are now trying to format our code. If the code will be formatted only on master, backporting changes to 1.22 branch will be hard a little. I think we should format code before branching 1.22, at least once, with minimal requirement. — Masakazu On Wed, Jan 24, 2018 at 5:26

Re: [PROPOSAL] Planning for next releases

2018-01-23 Thread Sijie Guo
On Tue, Jan 23, 2018 at 9:45 AM, Matteo Merli wrote: > Ok, if there are no other volunteers, I can take over for 2.0 release. > > Does everyone agree in creating 1.22 branch early so that we can start > merging changes meant for 2.0? We would need to merge some changes in both > master & 1.22 bra

Re: [PROPOSAL] Planning for next releases

2018-01-23 Thread Matteo Merli
Ok, if there are no other volunteers, I can take over for 2.0 release. Does everyone agree in creating 1.22 branch early so that we can start merging changes meant for 2.0? We would need to merge some changes in both master & 1.22 branch for a short amount of time, but it shouldn't be that bad. M

Re: [PROPOSAL] Planning for next releases

2018-01-21 Thread Rajan Dhabalia
Hi, Yes, we can target 1.22.0-incubating release by reviewing and merging pending PRs by end of this month and then we can prepare for 2.0 release. >> Also, are there any volunteers for release managers for both releases? Sure, I can be release manager for 1.22.0-incubating. Thanks, Rajan On