I agree with @marqh but want to recognize that this should be, to some extent, at the discretion of the repository admins and issue moderators. I say this because a given change may have a different disposition with regard to the current document depending on the state the overall project is in at the time. e.g. we are working hard on v2.0 but v1.9 is about done. I wouldn't want to 100% pre-judge how people want to use branches for a given PR at that point in the future.
So -- 1. PRs get opened against master which should be even with or recognizably ahead the latest release. 1. past releases are tags on master. No branch needed because we don't bug fix old releases. 1. branches are used as short and/or long term feature development space. 1. approved changes are merged to master as soon as possible after acceptance. Then the question is, should we add something to this affect to [CONTRIBUTING.md](https://github.com/cf-convention/cf-conventions/pull/137/files?short_path=8cc7b2b#diff-8cc7b2b0d78dd2501610391c086a8516)? -- 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-412947016
