-d switch isn't accurately described

Matthew - Do you have an idea on how we might word what '-d' will now do? Without any outside input I might use something like "Upgrade to the development release of Ubuntu if running the release preceding it". Thanks!

That seems good to me. Slightly shorter would be “If using the current Ubuntu release, upgrade to the development version”.

On Wed, Jun 28, 2017 at 07:42:51AM -0000, Matthew Paul Thomas wrote:
> That seems good to me. Slightly shorter would be “If using the current
> Ubuntu release, upgrade to the development version”.

I think "the current" release isn't specific enough as right now we have
three "current" releases - Xenial, Yakkety, and Zesty.

--
Brian Murray

Oh great, both update-manager and do-release-upgrade (both from different packages) have the -d documentation. This'll need fixing in both packages then.

This bug was fixed in the package ubuntu-release-upgrader - 1:17.10.6

---------------
ubuntu-release-upgrader (1:17.10.6) artful; urgency=medium

  * Fix new pep8 failures in artful - E722 do not use bare except.
  * Update the manpage regarding '-d' change.

 -- Brian Murray <email address hidden> Thu, 13 Jul 2017 15:49:23 -0700

This bug was fixed in the package update-manager - 1:17.10.1

---------------
update-manager (1:17.10.1) artful; urgency=medium

  [ Steve Langasek ]
  * ubuntu-support-status: instead of checking the Release timestamp in
    the releases file for every single package on the system, get the
    release date from distro-info-data because it will always be the same.
    This speeds up the script by > 50% in testing.

  [ Brian Murray ]
  * update-manager: Clarify that the "-d" switch is only for upgrading from
    the latest supported release to the development release, not any release.
    (LP: #1700829)
  * Remove --sandbox (aufs support) as it has been broken for some time and
    was rather unused. (LP: #1605259)

 -- Brian Murray <email address hidden> Wed, 12 Jul 2017 15:03:18 -0700

Hello Brian, or anyone else affected,

Accepted update-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:16.04.7 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Brian, or anyone else affected,

Accepted update-manager into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:17.04.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Brian, or anyone else affected,

Accepted ubuntu-release-upgrader into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:17.04.9 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Brian, or anyone else affected,

Accepted ubuntu-release-upgrader into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:16.04.22 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Using update-manager and ubuntu-release-upgrader from zesty-proposed I confirmed that the new documentation about the '-d' switch is correct and displays as expected.

Using update-manager and ubuntu-release-upgrader from xenial-proposed I confirmed that the new documentation about the '-d' switch is correct and displays as expected.

I also tested upgrading using 'do-release-upgrade -d' and saw the error message regarding "the latest supported release".

This bug was fixed in the package ubuntu-release-upgrader - 1:16.04.22

---------------
ubuntu-release-upgrader (1:16.04.22) xenial; urgency=medium

  * do-release-upgrade: Clarify that the "-d" switch is only for upgrading
    from the latest supported release to the development release, not any
    release. Additionally, provide a specific error message if run with -d and
    not running the latest supported release. (LP: #1700829)

 -- Brian Murray <email address hidden> Fri, 14 Jul 2017 16:46:34 -0700

The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package update-manager - 1:16.04.7

---------------
update-manager (1:16.04.7) xenial; urgency=medium

  * update-manager: Clarify that the "-d" switch is only for upgrading from
    the latest supported release to the development release, not any release.
    (LP: #1700829)

 -- Brian Murray <email address hidden> Mon, 17 Jul 2017 09:31:17 -0700

This bug was fixed in the package update-manager - 1:17.04.4

---------------
update-manager (1:17.04.4) zesty; urgency=medium

  * update-manager: Clarify that the "-d" switch is only for upgrading from
    the latest supported release to the development release, not any release.
    (LP: #1700829)

 -- Brian Murray <email address hidden> Fri, 14 Jul 2017 16:51:54 -0700

This bug was fixed in the package ubuntu-release-upgrader - 1:17.04.9

---------------
ubuntu-release-upgrader (1:17.04.9) zesty; urgency=medium

  * do-release-upgrade: Clarify that the "-d" switch is only for upgrading
    from the latest supported release to the development release, not any
    release. Additionally, provide a specific error message if run with -d and
    not running the latest supported release. (LP: #1700829)

 -- Brian Murray <email address hidden> Fri, 14 Jul 2017 16:33:50 -0700