jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 07:17:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update instructions

Browse Source
This commit is contained in:
Fabian Affolter 2017-10-07 21:58:52 +02:00
parent 678c6abd22
commit 3963d98d7d
No known key found for this signature in database
GPG Key ID: DDF3D6F44AAB1336
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/developers/releasing.markdown
View File

@ -36,7 +36,7 @@ This page describes the steps for publishing a new Home Assistant release. Those
1. Create a blog post in the release branch and base it on the text of the PR in the main repository. Add images, additional text, links, etc. if it adds value. Tag each platform/component in a message to documentation. 1. Create a blog post in the release branch and base it on the text of the PR in the main repository. Add images, additional text, links, etc. if it adds value. Tag each platform/component in a message to documentation.
2. Create missing documentation as stubs. 2. Create missing documentation as stubs.
3. Update `config.yml` with link to the new release blog post and version number (at the bottom of the file). 3. Update `_config.yml` with link to the new release blog post and version number (at the bottom of the file).
4. Merge `current` into release branch (`$ git checkout release-0-40 && git merge current`) to make the PR mergeable. 4. Merge `current` into release branch (`$ git checkout release-0-40 && git merge current`) to make the PR mergeable.
5. Merge pull request (blog post, updated frontpage, and all new documentation) to `current`. DO NOT SQUASH! 5. Merge pull request (blog post, updated frontpage, and all new documentation) to `current`. DO NOT SQUASH!
6. Run `credits_generator`. 6. Run `credits_generator`.