>I propose something inspired by Git Flow, roughly as follows: >master is the current release. >next is the next release, an "editor's draft", if you will.
I don't think we need a `next` branch. Each new convention version will be a tagged release in the master branch thus allowing this branch to represent the Editor's Draft. All the new material merged into the master branch after the last release is assumed to be accepted for the next release, barring any stylistic or formatting changes. The process would go something like this: 1. Anyone who wants to propose a change to the convention should fork this repository. (I assume the number of those with commit privileges will be small so forking is what majority will have to do.) 1. Create a branch off the master in the forked repository and work on the proposed changes in this new branch. 1. Creating a pull request to the upstream (the official convention's) repository initiates the formal review process of the proposed changes. 1. Pull request creator is responsible for updating its branch and the text of the changes with the upstream's master branch during the review process. 1. The review process ends when the pull request branch is merged into the upstream's `master` branch. It would be good to appoint, at least nominally, a few editors for every new convention release. They would be in charge of preparing the text in the master branch for the next release and making sure the review process of any open pull request is reasonably timely. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/130#issuecomment-399197009
