New version release procedure#588
Open
davidhassell wants to merge 12 commits intocf-convention:mainfrom
Open
Conversation
RELEASE.md
Outdated
|
|
||
| ## Copy the new documents to the website repository | ||
|
|
||
| Go to your fork of https://github.com/cf-convention/cf-convention.github.io, create a new branch from "main", copy the new documents into this branch and submit the changes as a puull request back to https://github.com/cf-convention/cf-convention.github.io. The following is an example of how this may be done, but other git formulations are possible: |
davidhassell
commented
Jan 24, 2025
Contributor
|
@davidhassell to me this PR it's ready to be merged |
| - "Choose a tag" for the new version on the "main" branch: The tag should be called `v<VN>.0`, substituting `<VN>` with the release version (e.g. `v1.12.0`). | ||
| - Set the release title to `CF-<VN>`, substituting `<VN>` the release version (e.g. `CF-1.12`). | ||
| - Click "Generate release notes". This will automatically generate a description of the release. | ||
| - Edit the description to remove the list of contributors, instead adding any new people who have made substantive contributions to the list at http://cfconventions.org/conventions_contributors.html. |
Contributor
There was a problem hiding this comment.
Is this the same thing as at line 134?
| - In file **history.adoc**, insert a new heading at the top of the section: `=== Working version (most recent first)` | ||
|
|
||
| - For any issue which has been incorporated in the new release: | ||
| - If the issue has a `new contributor` label, add the new contributor(s) to the list at https://cfconventions.org/conventions_contributors.html. |
|
|
||
| - For any issue which has been incorporated in the new release: | ||
| - If the issue has a `new contributor` label, add the new contributor(s) to the list at https://cfconventions.org/conventions_contributors.html. | ||
| - Ensure that the issue is closed. |
Contributor
There was a problem hiding this comment.
Add the change agreed label to the issue, if not already there.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See issue #371 for discussion of these changes.
Release checklist
cf-conventions.adoc? Add in two places: on line 3 and under.Additional AuthorsinAbout the authors.cf-conventions.adocup to date? Versioning inspired by SemVer.history.adocup to date?For maintainers
After the merge remember to delete the source branch.
Tags are set at the conclusion of the annual meeting; until then,
mainalways is a draft for the next version.