Manpages for juju aliases drop version
Bug #1570651 reported by
Martin Packman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Won't Fix
|
Medium
|
Unassigned | ||
juju-core |
Won't Fix
|
Undecided
|
Unassigned | ||
1.25 |
Won't Fix
|
Undecided
|
Unassigned | ||
juju-core (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
With xenial, we now provide juju version specific wrappers named 'juju-1' and 'juju-2.0' that have corresponding manpages. However, the text inside the pages just uses 'juju' as the name, not the alias, which is particularly confusing for juju-1 where the commands will often differ.
The documentation generation step should ideally take a name which juju will be invoked as and use that in place of 'juju' throughout.
Changed in juju-core: | |
importance: | Undecided → Medium |
milestone: | none → 2.0-rc1 |
status: | New → Triaged |
tags: | added: docs |
tags: | added: packaging |
Changed in juju-core: | |
milestone: | 2.0-beta5 → 2.0-rc1 |
Changed in juju-core: | |
milestone: | 2.0-beta6 → 2.0-beta7 |
Changed in juju-core: | |
milestone: | 2.0-beta7 → 2.0-beta8 |
Changed in juju-core: | |
milestone: | 2.0-beta8 → 2.0-beta9 |
Changed in juju-core: | |
milestone: | 2.0-beta9 → 2.0-beta10 |
Changed in juju-core: | |
milestone: | 2.0-beta10 → 2.0-beta11 |
Changed in juju-core: | |
milestone: | 2.0-beta11 → 2.0-beta12 |
Changed in juju-core: | |
milestone: | 2.0-beta12 → 2.0-beta13 |
Changed in juju-core: | |
milestone: | 2.0-beta13 → 2.0-beta14 |
Changed in juju-core: | |
milestone: | 2.0-beta14 → 2.0-beta15 |
Changed in juju-core: | |
milestone: | 2.0-beta15 → 2.0.0 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.0 → none |
milestone: | none → 2.0.0 |
Changed in juju-core: | |
status: | New → Won't Fix |
Changed in juju: | |
milestone: | 2.0.0 → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
To post a comment you must log in.
going forward, we are not likely to make this change.