Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue345+371 #4

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,8 +45,12 @@ Use of other branches is at the discretion of the repository administrators.

When an issue and accompanying pull request concludes with an agreed change to the conventions, the pull request is merged into the master branch according to the [Rules for CF Convention Changes](http://cfconventions.org/rules.html).

The pull request is merged by a member of the Governance Panel or the CF Conventions and Standard Names Committee.
The person who merges the pull request also closes the issue.
The pull request is merged by a member of the Governance Panel or the CF Conventions and Standard Names Committee. That person carries out these tasks:

* Set a milestone of the next release on the pull request.
* Merge the pull request.
* Label the issue with `change agreed`.
* Close the issue.

If subsequent discussion is required after the pull request has been merged then a new issue should be raised, rather than reopening the closed issue.
An issue may be closed without the merging of a pull request if the change was not accepted by the community.
Expand Down