From 2b4fb8770ca52b5a8e56f84dd48b053c147be3a0 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 13 Jul 2016 19:34:42 +0200 Subject: [PATCH] Change ordering --- source/developers/releasing.markdown | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/source/developers/releasing.markdown b/source/developers/releasing.markdown index 93e0f47fa40..5c0fec8b407 100644 --- a/source/developers/releasing.markdown +++ b/source/developers/releasing.markdown @@ -22,9 +22,10 @@ This page describes the steps for publishing a new Home Assistant release. 1. Create a blog post and base it on the PR text. Add images, additional text, links, etc. if it adds value. Tag each platform/component in message to documentation. 2. Create missing documentation as stumbs. -3. Update the link on the frontpage (`source/index.html`) to link to the new release blog post and version number. -4. Merge blog post and updated frontpage to `master` (`git merge next`). -5. Change to `next` and merge with `master` (`git checkout next && git merge master`) to keep in sync. +3. Create a pull request from `next` to `master` with the upcoming release number as title. +4. Merge `master` into `next` (`git checkout next && git merge master`) to make the PR mergable. +5. Update the link on the frontpage (`source/index.html`) to link to the new release blog post and version number. +6. Merge blog post and updated frontpage to `master` (`git merge next`). ### {% linkable_title Python Package Index %}