Hi Owen, Thanks for bringing this up!
Given our track record, instability we have seen in the pipeline recently and that the holidays are coming up, I wonder if it makes sense to give the release more time to stabilize and cut the branch even earlier. Maybe we could try to find a release manager early next week and cut it Oct 25th? Thoughts? On Fri, Oct 18, 2019 at 12:25 PM Owen Nichols <onich...@pivotal.io> wrote: > Geode's stated policy < > http://apache.org/foundation/records/minutes/2018/board_minutes_2018_11_21.txt> > is to cut quarterly release branches on a time-based schedule > (specifically, the Monday on or after Feb 1, May 1, Aug 1, Nov 1). > > Here’s a potential timeline: > > Now > [Contributors] Start thinking about how to make features already in > develop as stable as possible. > [Contributors] Hold off on merging new potentially-destabilizing work > until after the branch is cut. > [All] Start a DISCUSS thread if you want to propose changes to release > cadence, release process, or the timing of this release specifically. > > Mon Oct 28 > Call for someone to volunteer to be the 1.11 Release Manager. No prior > experience needed! Unforgettable adventure guaranteed! > Release manager begins working through > https://cwiki.apache.org/confluence/display/GEODE/Releasing+Apache+Geode > > Mon Nov 4 > Cut release/1.10.0 branch (only critical fixes accepted from this point > forward) > > Thu Nov 21 (estimate; actual date depends how many critical fixes must be > brought in to stabilize the release branch) > 1.11.0.RC1 > > Thu Dec 5 (estimate; actual date depends how many RC's it takes) > Officially release 1.11.0
