Server versioning and development/release/maintenance model

@Kelsey_Schubert Thanks for the reply.

I can see how versioning is done and I’m wondering how development is done.

For example, on GitHub, branch v6.1 is 137 commits ahead and 1161 commits behind master branch.

Do all the active branches cherrypick off the master branch? If a developer was to make a new feature, where is the start? … a new personal branch of master that will one day, hopefully, be merged back into master? If a developer creates a fix applicable to multiple branches/releases, is it first developed as a branch of master, then merged back into master and then cherrypicked into all the active branches?

Cheers!