Review/-write section about upgrading

[Pasi Lallinaho]

Currently, the section about upgrading [1] only covers upgrading to the next regular release. There should be
1) more information about the regular and LTS releases and the different upgrade paths
2) some thoughts when it's wise to use the one or the other and finally,
3) clear instructions for upgrading to both an LTS and a regular release

[1] http://docs.xubuntu.org/1404/migrating-upgrading.html#upgrading

[Pasi Lallinaho (knome)]

One way to make the section more legible for the end-user would be to split up the section as following:

== Upgrading from an older version of Xubuntu ==
[paragraph or two about release cadence for regular and LTS releases and upgrade paths]

then subsections:
- Upgrading to an LTS release
- Upgrading to a regular release
- Upgrading to a development release

[Launchpad Janitor (janitor)]

This bug was fixed in the package xubuntu-docs - 15.04

---------------
xubuntu-docs (15.04) vivid; urgency=medium

  [ Pasi Lallinaho ]
  * Bump version information to 15.04 Vivid Vervet
  * Attribute documentation correctly for the Xubuntu Documentation team
  * Clean up some files
  * Remove unused entities, directories and files
  * Add responsive stylesheets for the documentation
  * Tweak some CSS definitions
  * Replace the caution/important image with a new image
    from upstream (elementary-xfce)
  * Add responsive stylesheets for the start page
  * Add an id for the legalnotice tag to output specified filename
  * Improve the wording on releases on the upgrades section

  [ David Pires ]
  * Corrected a typo in the 'Changing update frequency and behavior'
    sub-section of the Managing installed applications chapter
  * Re-write the update-configuration-notifications section of the
    Managing installed applications chapter
  * Rephrased the first paragraph in index.html
  * Removed all the entries related to gthumb from xubuntu.ent
  * Corrected a typo in internet-networks.xml

  [ Elfy ]
  * Update the "Upgrading" section to be comprehensive. (LP: #1385479)

  [ Unit 193 ]
  * Move validation to a 'test' target, don't run at build time.
  * scripts/translators: Create a fallback in case no translators are found.
  * network-troubleshooting section: 'nm-tool' ➞ 'nmcli device show'
  * Lower the required translation percentage to 70.

  [ Steve Dodier-Lazaro ]
  * Update the security guide.
 -- Sean Davis <email address hidden> Mon, 09 Mar 2015 20:33:59 -0400