Support co-installable wind clients
Bug #1572700 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Won't Fix
|
High
|
Unassigned | ||
| juju-release-tools |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
We want to support Juju 1.x and 2.x on Windows. The inno setup script will need a new UUID for AppId and to set a new install directory. By updating the master (2.x) branch, Ci will automatically discover and use different rules from 1.x We want a test to verify the two jujus are co-installed. This might be nothing more than checking that the current testing host always has juju 1 and juju2 installed.
We may need to choose new .exe names to allow users to call both.
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.0.0 |
| Changed in juju-release-tools: | |
| importance: | High → Medium |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0.0 → none |
| milestone: | none → 2.0.0 |
Revision history for this message
| Alexis Bruemmer (alexis-bruemmer) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Incomplete |
| Changed in juju: | |
| milestone: | 2.0-rc3 → 2.0.0 |
| Changed in juju: | |
| milestone: | 2.0.0 → none |
| Changed in juju: | |
| status: | Incomplete → Won't Fix |
| Changed in juju-release-tools: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
Curtis, What changes need to be made in juju core to support co-installable windows clients?