From 0bff923f5246cd684c7b473b812ca9780a4060a2 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 21 Sep 2016 08:17:57 -0700 Subject: [PATCH] Update releasing.markdown --- source/developers/releasing.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/releasing.markdown b/source/developers/releasing.markdown index d1d53f65e97..9e35157920b 100644 --- a/source/developers/releasing.markdown +++ b/source/developers/releasing.markdown @@ -16,7 +16,7 @@ This page describes the steps for publishing a new Home Assistant release. 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. Update `homeassistant/const.py` with the correct version number (remove the the `dev` tag) and push that commit. -4. Merge pull request. +4. Merge pull request (DO NOT SQUASH!). 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 marker for the next release. 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.