From 87d999f3ef05bdd05d3658a8e828d7f24057c676 Mon Sep 17 00:00:00 2001
From: Daniel Shokouhi
Date: Tue, 20 Feb 2018 16:15:35 -0800
Subject: [PATCH 1/4] Add some emphasis about Breaking Changes
We should provide proper guidance to the user about the importance of release notes and paying attention to breaking changes. A common error users face while updating home assistant is not paying attention to the breaking changes. If the user has not done an update in sometime they may also forget about previous breaking changes that still stand.
---
source/_docs/installation/updating.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_docs/installation/updating.markdown b/source/_docs/installation/updating.markdown
index a23aa31b27f..4750a812913 100644
--- a/source/_docs/installation/updating.markdown
+++ b/source/_docs/installation/updating.markdown
@@ -14,7 +14,7 @@ redirect_from: /getting-started/updating/
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [Hass.io](/hassio/), [HASSbian](/docs/hassbian/common-tasks/#update-home-assistant), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant).
-View what's new in the latest version and potential impacts on your system [here](https://github.com/home-assistant/home-assistant/releases).
+View what's new in the latest version and potential impacts on your system [here](https://github.com/home-assistant/home-assistant/releases). It is in good practice to review the release notes and pay close attention to the Breaking Changes that are listed there. If you have not done an update in sometime, you should also look at previous release notes as they can also have Breaking Changes that may impact your system. Breaking Changes may require configuration updates for your components, if not done before the update home assistant may not load or the component will not work.
The default way to update Home Assistant to the latest release, when available, is:
From 6a2c0478893fffc7abf8ae20b26fdf4d7cd2744f Mon Sep 17 00:00:00 2001
From: Daniel Shokouhi
Date: Tue, 20 Feb 2018 16:20:44 -0800
Subject: [PATCH 2/4] Add capital letters for Home Assistant
oops :)
---
source/_docs/installation/updating.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_docs/installation/updating.markdown b/source/_docs/installation/updating.markdown
index 4750a812913..d3a271544d8 100644
--- a/source/_docs/installation/updating.markdown
+++ b/source/_docs/installation/updating.markdown
@@ -14,7 +14,7 @@ redirect_from: /getting-started/updating/
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [Hass.io](/hassio/), [HASSbian](/docs/hassbian/common-tasks/#update-home-assistant), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant).
-View what's new in the latest version and potential impacts on your system [here](https://github.com/home-assistant/home-assistant/releases). It is in good practice to review the release notes and pay close attention to the Breaking Changes that are listed there. If you have not done an update in sometime, you should also look at previous release notes as they can also have Breaking Changes that may impact your system. Breaking Changes may require configuration updates for your components, if not done before the update home assistant may not load or the component will not work.
+View what's new in the latest version and potential impacts on your system [here](https://github.com/home-assistant/home-assistant/releases). It is in good practice to review the release notes and pay close attention to the Breaking Changes that are listed there. If you have not done an update in sometime, you should also look at previous release notes as they can also have Breaking Changes that may impact your system. Breaking Changes may require configuration updates for your components, if not done before the update Home Assistant may not load or the component will not work.
The default way to update Home Assistant to the latest release, when available, is:
From 479334e8692c24749a604d973f7325679b8ea6de Mon Sep 17 00:00:00 2001
From: Daniel Shokouhi
Date: Tue, 20 Feb 2018 17:14:23 -0800
Subject: [PATCH 3/4] updates
---
source/_docs/installation/updating.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_docs/installation/updating.markdown b/source/_docs/installation/updating.markdown
index d3a271544d8..2c3fd01c2e3 100644
--- a/source/_docs/installation/updating.markdown
+++ b/source/_docs/installation/updating.markdown
@@ -14,7 +14,7 @@ redirect_from: /getting-started/updating/
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [Hass.io](/hassio/), [HASSbian](/docs/hassbian/common-tasks/#update-home-assistant), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant).
-View what's new in the latest version and potential impacts on your system [here](https://github.com/home-assistant/home-assistant/releases). It is in good practice to review the release notes and pay close attention to the Breaking Changes that are listed there. If you have not done an update in sometime, you should also look at previous release notes as they can also have Breaking Changes that may impact your system. Breaking Changes may require configuration updates for your components, if not done before the update Home Assistant may not load or the component will not work.
+View what's new in the latest version and potential impacts on your system in [release notes](https://github.com/home-assistant/home-assistant/releases). It is in good practice to review the release notes and pay close attention to the **Breaking Changes** that are listed there. If you have not done an update in sometime, you should also look at previous release notes as they can also have **Breaking Changes** that may impact your system. **Breaking Changes** may require configuration updates for your components, if not done before the update Home Assistant may not load or the component will not work.
The default way to update Home Assistant to the latest release, when available, is:
From 4880ebda59a66471b50c56e4dca7cc4d2460be11 Mon Sep 17 00:00:00 2001
From: c727
Date: Wed, 21 Feb 2018 05:58:50 +0100
Subject: [PATCH 4/4] Update updating.markdown
---
source/_docs/installation/updating.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_docs/installation/updating.markdown b/source/_docs/installation/updating.markdown
index 2c3fd01c2e3..dafb485e009 100644
--- a/source/_docs/installation/updating.markdown
+++ b/source/_docs/installation/updating.markdown
@@ -14,7 +14,7 @@ redirect_from: /getting-started/updating/
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [Hass.io](/hassio/), [HASSbian](/docs/hassbian/common-tasks/#update-home-assistant), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant).
-View what's new in the latest version and potential impacts on your system in [release notes](https://github.com/home-assistant/home-assistant/releases). It is in good practice to review the release notes and pay close attention to the **Breaking Changes** that are listed there. If you have not done an update in sometime, you should also look at previous release notes as they can also have **Breaking Changes** that may impact your system. **Breaking Changes** may require configuration updates for your components, if not done before the update Home Assistant may not load or the component will not work.
+Check what's new in the latest version and potentially impacts your system in [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases). It is good practice to review these release notes and pay close attention to the **Breaking Changes** that are listed there. If you havn't done an update for a while, you should also check previous release notes as they can also contain relevant **Breaking Changes**. **Breaking Changes** may require configuration updates for your components. If you missed this and Home Assistant refuses to start, check `/home-assistant.log` for details about broken components.
The default way to update Home Assistant to the latest release, when available, is: