This issue supersedes #172 and is implemented by #256. The larger changes to the CF governance process discussed at length in #172 have been pursued in a separate activity. I would like to capture the procedural changes affecting how we use GitHub that were discussed (and, I believe, mostly agreed) here.
People who have expressed interest in the original issue: @castelao @davidhassell @JonathanGregory @ethanrd @dblodgett-usgs @martinjuckes @DocOtak @kevin-obrien @marqh @zklaus People who expressed explicit support in their comments on that issue: @DocOtak @ngalbraith # Summary of changes in PR ## Implementation in GitHub / procedural stuff - [x] **Do we use semver?**Yes, but we shouldn't get hung up on it. Now we say we're "inspired by semver". - [x] **Checklist before merges?** Yes. Edit `history.adoc`, update authors, etc. in PR template. - [x] **How do we ensure that issues are dealt with in a timely fashion?** Attach the release frequency to the meeting so that changes actually come in. Note explicitly that pre-annual meeting 3 week feature freeze is a feature freeze. Tag stuff for milestones, that's motivating, and it summarises upcoming changes. - [x] **Who sets tags and when?** Secretary, 6 weeks after annual meeting. - [x] **When do we delete branches?** Whenever we want as long as they're not protected. Normally after merging. Questions that in the #172 were considered interesting but are not addressed here: - Who owns docs from the website? - Align descriptive language in `CONTRIBUTING.md` with GH roles? -- 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/257 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
