Could be: * not very many fixes have come in, so maybe there’s actually nothing further we’re waiting for? * to give us a better chance of hitting Dec 2 goal, in case it takes more than one RC? * some people might prefer to give feedback against a formal RC rather than informally against the branch? * impact of Thanksgiving?
> On Nov 12, 2019, at 4:05 PM, Alexander Murmann <ajmurm...@gmail.com> wrote: > > I think it's really great to agree on the date by which we want to have a > RC1 early. However, I thought the target release date is beginning of > December, which would probably bring us to December 2nd, given the first is > a Sunday. The voting period is 3 days. I would have expected that we'd > create the RC around 11/26 (with the caveat that everything looks fine by > then). What's the reasoning behind cutting it so early? > > On Tue, Nov 12, 2019 at 3:47 PM Owen Nichols <onich...@pivotal.io> wrote: > >> +1 for cutting RC1 within two weeks of creating the release branch :) >> >>> On Nov 12, 2019, at 3:00 PM, Mark Hanson <mhan...@pivotal.io> wrote: >>> >>> Hello Geode Dev Community, >>> >>> We have a release branch for Apache Geode 1.11.0 - “release/1.11.0”. >> People have been voting to pick up fixes and I have been cherry picking >> them accordingly. I think it is important that we look forward to a release >> date and I have picked November 19th, 2019 as a time to try for. As with >> any process, if a sufficiently scary issue comes up we will reschedule, but >> this seems like a reasonable date. >>> >>> As always, please contact me with any concerns you might have. If no >> concerns are raised, we will start voting on the release on November 20th, >> 2019. >>> >>> Regards >>> Mark Hanson >>> >> >> > > -- > Alexander J. Murmann > (650) 283-1933
