Merge lp:~paelzer/serverguide/serverguide-16.04-do-release-upgrade into lp:serverguide/trunk

Proposed by Christian Ehrhardt 
Status: Merged
Approved by: Doug Smythies
Approved revision: 290
Merged at revision: 292
Proposed branch: lp:~paelzer/serverguide/serverguide-16.04-do-release-upgrade
Merge into: lp:serverguide/trunk
Diff against target: 16 lines (+6/-0)
1 file modified
serverguide/C/installation.xml (+6/-0)
To merge this branch: bzr merge lp:~paelzer/serverguide/serverguide-16.04-do-release-upgrade
Reviewer Review Type Date Requested Status
Doug Smythies Approve
Review via email: mp+293907@code.launchpad.net

Commit message

clarify do-release-update details that are slightly special for an LTS release

Description of the change

We realized today that many know how the do-release-upgrade is special for LTS, but it is not properly documented other than a few ask Ubuntu posts.

This change is meant to clarify that in at least one of our docs (not sure if more should get that info).

To post a comment you must log in.
Revision history for this message
Doug Smythies (dsmythies) wrote :

O.K. Thanks very much

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== modified file 'serverguide/C/installation.xml'
--- serverguide/C/installation.xml 2016-04-12 15:05:41 +0000
+++ serverguide/C/installation.xml 2016-05-05 14:48:11 +0000
@@ -407,6 +407,12 @@
407 Upgrading to a development release is <emphasis>not</emphasis> recommended for production environments.407 Upgrading to a development release is <emphasis>not</emphasis> recommended for production environments.
408 </para>408 </para>
409 </warning>409 </warning>
410 <para>
411 For further stability of a LTS release there is a slight change in behaviour if you are currently running a LTS version.
412 LTS systems are only automatically considered for an upgrade to the next LTS via <application>do-release-upgrade</application> with the first point release.
413 So for example 14.04 will only upgrade once 16.04.1 is released.
414 If you want to update before, e.g. on a subset of machines to evaluate the LTS upgrade for your setup the same argument as an upgrade to a dev release has to be used via the <emphasis>-d</emphasis> switch.
415 </para>
410 </sect2>416 </sect2>
411 </sect1>417 </sect1>
412 <sect1 id="advanced-installation" status="review">418 <sect1 id="advanced-installation" status="review">

Subscribers

People subscribed via source and target branches