Hi Aaron, thank you for bringing your request and concern. Geode's release process dictates a time-based schedule to cut release branches. Once cut, the “critical fixes” rule does allow those to be brought
to the release branch by proposal on the dev list. If there is consensus from the Geode community that your proposed change satisfies the “critical fixes” rule we can bring it to the 1.10.0 release branch. There are a number of issues that will likely bring in other changes this week. Udo can still vote -1 and hope any future Spring requests won't be affected :^) I'll be unavailable the rest of the week starting tomorrow so Dan will assist with approved merges to 1.10 until Owen is back on Monday. Regards Dick Cavender On Tue, Aug 13, 2019 at 5:32 PM Udo Kohlmeyer <u...@apache.com> wrote: > @Aaron, is this an existing issue (i.e this was not introduced in a > current refactor)? > > If the answer is anything other that "This will make the system stop > working", I would vote: -1 > > If this is an existing issue and has been around for a while, I think we > hold off including this. > > I think the boat has sailed on the inclusion of issues into the 1.10 > release. Sorry... > > --Udo > > On 8/13/19 4:58 PM, Aaron Lindsey wrote: > > I’d like to propose including > https://github.com/apache/geode/pull/3913/commits/6f1814d1f719cc06b13769c40a9d6d01f99f927c > < > https://github.com/apache/geode/pull/3913/commits/6f1814d1f719cc06b13769c40a9d6d01f99f927c> > in the Geode 1.10 release. > > > > This commit fixes an issue where a NullPointerException is thrown from > PartitionedRegion.getLocalSize() when the statistics callback sampler is > invoked before a PartitionedRegion is initialized. > > > > - Aaron > > > > > > >
