You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/developers/releasing.markdown
+25-14Lines changed: 25 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -11,34 +11,45 @@ footer: true
11
11
12
12
This page describes the steps for publishing a new Home Assistant release.
13
13
14
+
### {% linkable_title GitHub (3 days before release) %}
15
+
16
+
1. Merge `master` into `dev` to make the PR mergeable.
17
+
2. Cut a release branch from `dev`. Example name `release-0-40`.
18
+
3. Create a pull request from release branch to `master` with the upcoming release number as the title. PR message contains intro, highlighting major changes, and an overview of all changes tagging each author.
19
+
4. Update `homeassistant/const.py` with the correct version number (remove the `dev` tag) and push that commit to release branch.
20
+
5. From now until the release branch has been merged, we tag bugfixes with the milestone for the release (create if doesn't exist)
21
+
22
+
### {% linkable_title Website (3 days before release) %}
23
+
24
+
1. Merge `current` into `next`
25
+
2. Cut release branch of `next`. For example `release-0-40`.
26
+
3. Open a PR from release branch to `current` with the upcoming release number as the title.
27
+
14
28
### {% linkable_title GitHub %}
15
29
16
-
1. Create a pull request from `dev` to `master` with the upcoming release number as the title.
17
-
2. Merge `master` into `dev` to make the PR mergeable. PR message contains intro, highlighting major changes, and an overview of all changes tagging each author.
18
-
3. Update `homeassistant/const.py` with the correct version number (remove the `dev` tag) and push that commit.
19
-
4. Merge pull request (DO NOT SQUASH!).
20
-
5. Then, after merged, push another update to `dev` of `homeassistant/const.py` that includes the next version with the `dev` tag. Add a meaningful commit message like "Version bump to X". This commit acts as a marker for the next release.
21
-
6. Go to [releases](https://github.com/home-assistant/home-assistant/releases) and tag a new release on the `master` branch. "Tag version" and "Release title" are the version number (`O.x` for major version, `0.x.y` for minor and bug fix releases). Release description is the text from PR. Press "Publish release" to finish the process.
30
+
1. Merge pull request (DO NOT SQUASH!).
31
+
2. Go to [releases](https://github.com/home-assistant/home-assistant/releases) and tag a new release on the `master` branch. "Tag version" and "Release title" are the version number (`O.x` for major version, `0.x.y` for minor and bug fix releases). Release description is the text from PR. Press "Publish release" to finish the process.
32
+
3. Merge `master` into `dev`.
22
33
23
34
### {% linkable_title Website %}
24
35
25
-
1. Create a blog post in `next` 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.
26
-
2. Create missing documentation as stumbs in `next`.
36
+
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.
37
+
2. Create missing documentation as stubs.
27
38
3. Update `config.yml` with link to the new release blog post and version number (at the bottom of the file).
28
-
4.Create a pull request from `next` to `current` with the upcoming release number as the title.
29
-
5. Merge `current` into `next` (`$ git checkout next && git merge current`) to make the PR mergeable.
30
-
6. Merge pull request (blog post, updated frontpage, and all new documentation) to `current`.
39
+
4.Merge `current` into release branch (`$ git checkout release-0-40 && git merge current`) to make the PR mergeable.
40
+
5. Merge pull request (blog post, updated frontpage, and all new documentation) to `current`.
41
+
6. Merge `current` into `next`.
31
42
32
43
### {% linkable_title Docker Hub %}
33
44
34
-
Create a new [tag](https://hub.docker.com/r/homeassistant/home-assistant/tags/) at https://hub.docker.com for the release.
45
+
Tags on Docker hub are automatically created when a release has been created on GitHub.
35
46
36
47
### {% linkable_title Python Package Index %}
37
48
38
49
Checkout the `master` branch and run `script/release` to publish the new release on [Python Package Index](https://pypi.python.org).
39
50
40
51
### {% linkable_title Social media %}
41
52
42
-
1. Create a [tweet](https://twitter.com/home_assistant) announcing blog post linking to release notes.
43
-
2. Publish a link to the tweet/release blog post for the [Google+ Community](https://plus.google.com/b/110560654828510104551/communities/106562234893511202708).
53
+
1. Use [hootsuite] to publish a link to the release post on social media.
0 commit comments