Sure! agree that we should hold the releases unless there is a critical issue.
This is not a gating issue and the code is already committed to develop. Sai On Thu, Nov 1, 2018 at 1:03 PM Alexander Murmann <amurm...@pivotal.io> wrote: > In the spirit of the previously discussed timed releases, we should only > hold cutting the release for critical issues, that for some reason (not > sure how that might be) should not be fixed after the branch has been cut. > Waiting for features leads us down the slippery slope we are trying to > avoid by having timed releases. Does that make sense? > > On Thu, Nov 1, 2018 at 12:45 PM Sai Boorlagadda <sai.boorlaga...@gmail.com > > > wrote: > > > I would like to resolve GEODE-5338 as it is currently waiting for > > doc update. > > > > Sai > > > > On Thu, Nov 1, 2018 at 10:00 AM Alexander Murmann <amurm...@pivotal.io> > > wrote: > > > > > Hi everyone, > > > > > > It's time to cut the release branch, since we are moving to time based > > > releases. Are there any reasons why a release branch should not be cut > as > > > soon as possible? > > > > > >
