> I favour creating a branch for the next version (e.g. 1.8) and specifying > that pull requests be made to this branch. This branch would be created as a > copy of the previous version (1.7) when that is released.
The "usual" git process (for code) is that a "release" is tagged (and maybe in its own branch, whereas "master" is used as the active copy -- being constantly updated -- when it it ready for a new version, a release is made. Kind of the point of "master" is that it is the default branch, that's seeing activer development. Why use a different workflow here?? -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/130#issuecomment-412924516
