cadey
/
nim-wiki
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated Creating a release (markdown)

This commit is contained in:
Dominik Picheta 2017-09-07 22:01:39 +01:00
parent dd78f5ab2f
commit 0143e3cddb
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Creating-a-release.md
View File

@ -42,7 +42,7 @@ PATH=$PATH:$(pwd)/bin
- Create a new blog post in `_drafts` titled: `version-<ver>-released.md` where `<ver>` is the version without any dots, e.g. `0180` for `0.18.0`. - Create a new blog post in `_drafts` titled: `version-<ver>-released.md` where `<ver>` is the version without any dots, e.g. `0180` for `0.18.0`.
- When ready to release: - When ready to release:
- move the blog post into `_posts` - move the blog post into `_posts`, making sure to append the current date to its filename: `2017-09-31-title.md`.
- modify config.yml's `version` key to the new version - modify config.yml's `version` key to the new version
- `git commit` - `git commit`
- **TIP:** Here is a real-life example of a commit that signifies a release: https://github.com/nim-lang/website/commit/6f95916dee1212dcf5465d74dcff14e01f714503. The draft blog post was created in earlier commits, but hopefully it's pretty easy to figure out how it was made. - **TIP:** Here is a real-life example of a commit that signifies a release: https://github.com/nim-lang/website/commit/6f95916dee1212dcf5465d74dcff14e01f714503. The draft blog post was created in earlier commits, but hopefully it's pretty easy to figure out how it was made.