I agree with the cutting the release branch, keep it sanitized from additional commits going into develop but ensure only these important critical fixes mentioned above in this chain makes it into the release branch.
For the second part, I am not sure how it was determined that fixes for GEODE-6391, GEODE-6393, GEODE-6369, GEODE-6404 contains risk of introducing more failures. Are we lacking tests , reviews etc. I apologize but I was not able to understand. Regards Nabarun On Thu, Feb 14, 2019 at 11:36 AM Alexander Murmann <amurm...@apache.org> wrote: > Usually I am a proponent of cutting a branch and then fixing things on > there where things are more stable. In this case we seem to have a large > number of fairly serious concerns. Do we think the cost of putting this > many fixes on develop + the release branch out-weights the benefit of less > risk of new issues being introduced? > > Thoughts? > > Thank you, Sai for taking over! > > On Thu, Feb 14, 2019 at 10:32 AM Sai Boorlagadda < > sai.boorlaga...@gmail.com> > wrote: > > > I volunteer to be the release manager for 1.9. > > > > Sai > > > > On Wed, Feb 13, 2019 at 7:48 PM Alexander Murmann <amurm...@apache.org> > > wrote: > > > > > If there are no other takers, I can act as release manager for 1.9 and > > will > > > cut a release branch this week. > > > > > > > > > On Tue, Jan 29, 2019 at 1:50 PM Alexander Murmann <amurm...@apache.org > > > > > wrote: > > > > > > > Hi everyone! > > > > > > > > February 1st is approaching rapidly which means it's almost time to > cut > > > > the 1.9 release. Who is interested in being the release manager for > > 1.9? > > > > > > > > Thank you! > > > > > > > > > >
