It looks like the discussion period ended Nov 25 with all comments in support,
so next phase is populating the proposed codeowners file. @Robert how long do
we have to populate this before you plan to formally propose activating it on
develop?
As prescribed I’ve submitted a PR[1] against the f
If someone wants to propose a list of must-fix Jira tickets before we can cut
the branch, I see that as a shift from a time-based to feature-based branch-cut
strategy. Might be fun to try?
Given the distributed nature of the Geode community, picking a date and
sticking to it allows decentraliz
Apologies if this detracts from the conversation of folks who have much more in
depth knowledge of the codebase than I do- please feel free to ignore if this
seems off base.
As a non-committing contributor who works mostly on code outside of core
Geode, it seems like an always shippable devel
