| 2015-01-29 18:16:10 |
Robie Basak |
bug |
|
|
added bug |
| 2015-01-29 18:16:21 |
Robie Basak |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-01-29 18:16:21 |
Robie Basak |
bug task added |
|
juju-core (Ubuntu Trusty) |
|
| 2015-01-29 18:16:27 |
Robie Basak |
juju-core (Ubuntu Trusty): assignee |
|
Robie Basak (racb) |
|
| 2015-01-29 18:16:50 |
Robie Basak |
bug |
|
|
added subscriber Wes |
| 2015-01-29 18:16:56 |
Robie Basak |
bug |
|
|
added subscriber Patricia Gaughen |
| 2015-01-29 18:17:03 |
Robie Basak |
bug |
|
|
added subscriber Alexis Bruemmer |
| 2015-01-29 18:17:23 |
Robie Basak |
bug |
|
|
added subscriber Curtis Hovey |
| 2015-03-11 03:06:36 |
Matthias Klose |
tags |
block-proposed upgrade-software-version |
upgrade-software-version |
|
| 2015-03-16 10:31:12 |
Robie Basak |
tags |
upgrade-software-version |
block-proposed upgrade-software-version |
|
| 2015-03-16 10:31:21 |
Robie Basak |
summary |
juju-core 1.21.1 is not packaged in Ubuntu |
juju-core 1.22.0 is not packaged in Ubuntu |
|
| 2015-03-16 10:32:02 |
Robie Basak |
description |
We're now in a position to have 1.21.1 enter trusty-proposed and vivid-proposed, but it should not land in trusty-updates or vivid until upstream passes QA on our proposed binaries, published 1.20.11 tools in their stable simplestream and announces the release for general production use.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Development Fix]
Full backport of new upstream release. racb will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Stable Fix]
Full backport of new upstream release.
[Pre-QA tasks]
[racb] Upload to the development release (vivid-proposed): TODO
[racb] Upload to the current LTS release (trusty-proposed): TODO
[QA Status]
Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.
[sinzui] Upsteam QA test against Vivid: TODO
[sinzui] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: TODO
[sinzui] Test juju-quickstart against trusty-proposed: TODO
The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.
Landscape team QA: ?TODO |
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-proposed, but it should not land in trusty-updates or vivid until upstream passes QA on our proposed binaries, published the tools in their stable simplestream and announces the release for general production use.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Development Fix]
Full backport of new upstream release. racb will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Stable Fix]
Full backport of new upstream release.
[Pre-QA tasks]
[racb] Upload to the development release (vivid-proposed): TODO
[racb] Upload to the current LTS release (trusty-proposed): POSTPONED
[QA Status]
Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.
[sinzui] Upsteam QA test against Vivid: TODO
[sinzui] Upstream QA test against Trusty: POSTPONED
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: TODO
[sinzui] Test juju-quickstart against trusty-proposed: POSTPONED
The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.
Landscape team QA: ?TODO |
|
| 2015-03-31 15:05:36 |
Robie Basak |
description |
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-proposed, but it should not land in trusty-updates or vivid until upstream passes QA on our proposed binaries, published the tools in their stable simplestream and announces the release for general production use.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Development Fix]
Full backport of new upstream release. racb will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Stable Fix]
Full backport of new upstream release.
[Pre-QA tasks]
[racb] Upload to the development release (vivid-proposed): TODO
[racb] Upload to the current LTS release (trusty-proposed): POSTPONED
[QA Status]
Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.
[sinzui] Upsteam QA test against Vivid: TODO
[sinzui] Upstream QA test against Trusty: POSTPONED
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: TODO
[sinzui] Test juju-quickstart against trusty-proposed: POSTPONED
The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.
Landscape team QA: ?TODO |
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-proposed, but it should not land in trusty-updates or vivid until upstream passes QA on our proposed binaries, published the tools in their stable simplestream and announces the release for general production use.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Development Fix]
Upload of new upstream release with packaging review. racb will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Stable Fix]
Full backport of new upstream release.
[Pre-QA tasks]
[strikov] Upload to the development release (vivid-proposed): DONE
[racb] Upload to the current LTS release (trusty-proposed): POSTPONED
[QA Status]
Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.
[sinzui] Upsteam QA test against Vivid: TODO
[sinzui] Upstream QA test against Trusty: POSTPONED
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: TODO
[sinzui] Test juju-quickstart against trusty-proposed: POSTPONED
The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.
Landscape team QA: ?TODO |
|
| 2015-03-31 15:05:43 |
Robie Basak |
juju-core (Ubuntu): status |
New |
Fix Committed |
|
| 2015-03-31 15:18:57 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/vivid-proposed/juju-core |
|
| 2015-04-06 22:08:57 |
Curtis Hovey |
description |
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-proposed, but it should not land in trusty-updates or vivid until upstream passes QA on our proposed binaries, published the tools in their stable simplestream and announces the release for general production use.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Development Fix]
Upload of new upstream release with packaging review. racb will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Stable Fix]
Full backport of new upstream release.
[Pre-QA tasks]
[strikov] Upload to the development release (vivid-proposed): DONE
[racb] Upload to the current LTS release (trusty-proposed): POSTPONED
[QA Status]
Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.
[sinzui] Upsteam QA test against Vivid: TODO
[sinzui] Upstream QA test against Trusty: POSTPONED
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: TODO
[sinzui] Test juju-quickstart against trusty-proposed: POSTPONED
The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.
Landscape team QA: ?TODO |
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-proposed, but it should not land in trusty-updates or vivid until upstream passes QA on our proposed binaries, published the tools in their stable simplestream and announces the release for general production use.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Development Fix]
Upload of new upstream release with packaging review. racb will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Stable Fix]
Full backport of new upstream release.
[Pre-QA tasks]
[strikov] Upload to the development release (vivid-proposed): DONE
[racb] Upload to the current LTS release (trusty-proposed): POSTPONED
[QA Status]
Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.
[sinzui] Upsteam QA test against Vivid: DONE
[sinzui] Upstream QA test against Trusty: POSTPONED
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: TODO
[sinzui] Test juju-quickstart against trusty-proposed: POSTPONED
The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.
Landscape team QA: ?TODO |
|
| 2015-04-06 23:09:56 |
Curtis Hovey |
description |
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-proposed, but it should not land in trusty-updates or vivid until upstream passes QA on our proposed binaries, published the tools in their stable simplestream and announces the release for general production use.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Development Fix]
Upload of new upstream release with packaging review. racb will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Stable Fix]
Full backport of new upstream release.
[Pre-QA tasks]
[strikov] Upload to the development release (vivid-proposed): DONE
[racb] Upload to the current LTS release (trusty-proposed): POSTPONED
[QA Status]
Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.
[sinzui] Upsteam QA test against Vivid: DONE
[sinzui] Upstream QA test against Trusty: POSTPONED
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: TODO
[sinzui] Test juju-quickstart against trusty-proposed: POSTPONED
The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.
Landscape team QA: ?TODO |
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-proposed, but it should not land in trusty-updates or vivid until upstream passes QA on our proposed binaries, published the tools in their stable simplestream and announces the release for general production use.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Development Fix]
Upload of new upstream release with packaging review. racb will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Stable Fix]
Full backport of new upstream release.
[Pre-QA tasks]
[strikov] Upload to the development release (vivid-proposed): DONE
[racb] Upload to the current LTS release (trusty-proposed): POSTPONED
[QA Status]
Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.
[sinzui] Upsteam QA test against Vivid: DONE
[sinzui] Upstream QA test against Trusty: POSTPONED
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: POSTPONED
The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.
Landscape team QA: ?TODO |
|
| 2015-04-07 11:12:12 |
Oleg Strikov |
tags |
block-proposed upgrade-software-version |
upgrade-software-version |
|
| 2015-04-07 17:50:06 |
Launchpad Janitor |
juju-core (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2015-07-28 17:35:15 |
Launchpad Janitor |
juju-core (Ubuntu Trusty): status |
New |
Fix Released |
|
