From bbfecba5cd3d897d29556bbd121236edf257c0a9 Mon Sep 17 00:00:00 2001 From: Robbie Trencheny Date: Thu, 12 Jan 2017 17:15:17 -0800 Subject: [PATCH] Update _config.yml now, not index.html --- 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 10cffe47535..1525f30b0e6 100644 --- a/source/developers/releasing.markdown +++ b/source/developers/releasing.markdown @@ -24,7 +24,7 @@ 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 a 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. +3. Update `config.yml` with link to the new release blog post and version number (at the bottom of the file). 4. Create a pull request from `next` to `current` with the upcoming release number as the title. 5. Merge `current` into `next` (`$ git checkout next && git merge current`) to make the PR mergeable. 6. Merge pull request (blog post, updated frontpage, and all new documentation) to `current`.