Suggest next major version upgrade

Bug #1532670 reported by Cheryl Jennings on 2016-01-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

If a new major version is available for an upgrade, users should be informed when they run the upgrade-juju command.

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0-alpha2
tags: added: 2.0 upgrade-juju
Changed in juju-core:
milestone: 2.0-alpha2 → 2.0-alpha3
Changed in juju-core:
milestone: 2.0-alpha3 → 2.0-beta4
Changed in juju-core:
milestone: 2.0-beta4 → 2.1.0
tags: removed: 2.0
tags: added: usability
affects: juju-core → juju
Changed in juju:
milestone: 2.1.0 → none
milestone: none → 2.1.0
Curtis Hovey (sinzui) on 2016-08-22
Changed in juju-core:
status: New → Won't Fix
no longer affects: juju-core/1.25
Anastasia (anastasia-macmood) wrote :

As there is no upgrade path at the moment between major versions, i.e. from 1.x to 2.x, I will remove our current milestone.
We will address it when upgrades are addressed.

Changed in juju:
milestone: 2.1.0 → none
importance: High → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers