On 2/22/24 09:25, Michael Jumper wrote:
On 2/22/24 08:16, Christopher Speck wrote:
As a community member and minor contributor this sounds good. I had a
few questions.
- Is there only ever a single patch version supported at a time?
Yes.
- Will there be a regular cadence of merging "main" into "next" so
actively developed work is up-to-date? Would this be done by core team
members or would community members be involved?
Yes to both. Just as we currently immediately merge changes to a
"staging/X.Y.Z" branch back to "master", changes to "main" would me
immediately merged to "next".
- With "next" being a single branch would it be all-or-nothing to
merge into "main", or would changes be cherry-picked for the next
up-coming version?
All-or-nothing, just like current "master".
When release time nears, there'd be a "staging/X.Y.Z" branch that
isolates the release scope from any other changes that might make their
way to any other branch, including "next", but I expect that'd be
relatively rare vs. changes to "patch" or "main".
Alrighty - with no objections, I'll move forward with creating/renaming
branches as necessary and documenting the new branching scheme. This
_should_ make things much more friendly and flexible.
- Mike
