juju-core 1.18 series
A future release of Juju.
Loading graph...
Series information
- Project:
- juju-core
- Series:
- 1.18
- Project drivers:
- Juju Project Lead
- Release manager:
- None
- Status:
- Obsolete
- Project development focus:
- is not the focus of development.
- Release URL pattern:
- None
Code for this series
The following branch has been registered as the mainline branch for this release series:
2298 revisions.
You can get a copy of the development focus branch using the command:
bzr branch lp://staging/juju-core/1.18
Milestones and releases
1 → 11 of 11 results | First • Previous • Next • Last |
Version | Expected | Released | Summary |
---|---|---|---|
juju-core 1.18.4 | 2014-06-02 | ||
juju-core 1.18.3 | 2014-05-08 | ||
juju-core 1.18.2 | 2014-04-29 | ||
juju-core 1.18.1 | 2014-04-11 | ||
juju-core 1.18.0 | 2014-04-04 | ||
juju-core 1.17.7 | 2014-03-28 | ||
juju-core 1.17.4 | 2014-02-28 | The release files were removed after it was discovered that trusty clients c... | |
juju-core 1.17.3 | 2014-02-21 | ||
juju-core 1.17.2 | 2014-01-30 | ||
juju-core 1.17.1 | 2014-01-24 | ||
juju-core 1.17.0 | 2013-12-21 | A development release that uses the API for all communication between clients... |
1 → 11 of 11 results | First • Previous • Next • Last |
All bugs Latest bugs reported
-
Bug #1339770: Machines are killed if mongo fails
Reported -
Bug #1400971: all agents except machine agent logging "INFO juju.worker.upgrader upgrader.go:121 desired tool version: 1.18.4.3" every 15 minutes following "juju upgrade-juju"
Reported -
Bug #1297559: upgrade-charm fails because of git
Reported -
Bug #1308146: not okForStorage error when deploying local charm
Reported -
Bug #1329282: MAAS + LXC containers == unable to upgrade charms due to git hostname resolution issues
Reported