Udo, it sounds like you would like to modify the release process to start the stabilization work on develop (rather than cutting the branch as the first step). I would love to hear community opinion on this proposal.
For 1.10, in the time we have cherry-picked 11 fixes to release/1.10.0, develop has seen over 90 commits. I believe due process has been followed in bringing only critical fixes to stabilize the release branch. Getting 1.10.0.RC1 into the hands of the community is the most important next step. If there are no further critical fix proposals, Dick and I would like to proceed with the RC1 this week. -Owen > On Aug 26, 2019, at 4:06 PM, Udo Kohlmeyer <u...@apache.com> wrote: > > Hi there Apache Geode devs, > > It has been some weeks since the proposed 1.10 release was cut. We've gone > through a few cycles where we keep on submitting "please include ticket > GEODE-XXX" because it is critical and will break the system. WHICH in reality > tells me that current develop is broken and unstable. > > I'm going to suggest that we abandon the current 1.10 release branch. I > cannot shake the feeling that our continuous cherry picking into a branch > will result in either the branch becoming unmaintainable, given we have only > select fixes in the branch OR we end up with a branch that is more stable > than our current development branch, which would result in us having to > rebase the develop branch onto the 1.10 branch. > > I propose that once we see the pipeline is clean and green for a solid we > then again attempt to cut 1.10 branch. > > We CANNOT continue adding to a branch in order to stabilize it.. It just > means the branch we cut from is unstable. If we cannot cut a branch from > develop without having to have weeks of stabilization cycles, then our main > branch is broken... > > Either way, not a good spot to be in. > > Thoughts? > > --Udo >
