home-assistant.io/source/developers/releasing.markdown

layout, title, description, date, sidebar, comments, sharing, footer

layout	title	description	date	sidebar	comments	sharing	footer
page	Releasing	Steps involved to publish a new Home Assistant release.	2016-07-13 17:00	true	false	true	true

This page describes the steps for publishing a new Home Assistant release.

{% linkable_title GitHub %}

1. Create a pull request from dev to master with the upcoming release number as title.
2. Merge master into dev to make the PR mergable. PR message contains intro, highlighting major changes, and an overview of all changes tagging each author.
3. Merge pull request.
4. Go to releases and tag a new release on the master branch. Tag name and title name are version number. Release description is text from PR.

{% linkable_title Website %}

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 message to documentation.
2. Create missing documentation as stumbs in next.
3. Update the link on the frontpage (source/index.html) to link to the new release blog post and version number.
4. Create a pull request from next to master with the upcoming release number as title.
5. Merge master into next ($ git checkout next && git merge master) to make the PR mergable.
6. Merge pull request (blog post, updated frontpage, and all new documentation) to master.

{% linkable_title Python Package Index %}

Checkout master branch and run script/release to publish the new release on Python Package Index

{% linkable_title Social media %}

1. Create a tweet announcing blog post linking to release notes.
2. Publish a link to the tweet/release blog post for the Google+ Community.