Comment 5 for bug 522910

The various Lucid release-notes pages now do include specific instructions for the direct hardy -> lucid upgrades.

So, that leaves just one wishlist suggestion: I wonder if it would make sense to update the comments in the /etc/update-manager/release-upgrades file to explain the situation more fully, e.g. something along these lines:

  # default prompting behavior, valid options:
  # never - never check for a new release
  # normal - check to see if a new release is available. If more than
  # one new release is found, the release upgrader will
  # attempt to upgrade to the release that immediately succeeds
  # the currently-running release.
  # lts - check to see if a new LTS release is available. The upgrader
  # will attempt to upgrade to the first LTS release available
  # after the currently-running one. (Note that this option
  # should not be used if the currently-running release is not
  # itself an LTS release, since in that case the upgrader won't
  # be able to determine if a newer release is available.)

(Or, perhaps it would be better to put the explaination of options into /usr/share/doc/update-manager-core/README , and replace the existing comments in the release-upgrades file with a pointer to that explaination.)