From 1a21aa0c0f9abacab055433644d4d2b85d048c14 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Fri, 26 Aug 2016 09:20:55 +0200 Subject: [PATCH] Update for repo changes --- source/developers/releasing.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/developers/releasing.markdown b/source/developers/releasing.markdown index e9cff8ecd94..17843777b13 100644 --- a/source/developers/releasing.markdown +++ b/source/developers/releasing.markdown @@ -25,9 +25,9 @@ This page describes the steps for publishing a new Home Assistant release. 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`. +4. Create a pull request from `next` to `current` with the upcoming release number as title. +5. Merge `current` 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 `current`. ### {% linkable_title Python Package Index %}