| 2015-06-29 14:36:40 |
Curtis Hovey |
bug |
|
|
added bug |
| 2015-06-29 14:37:16 |
Curtis Hovey |
branch linked |
|
lp:~sinzui/ubuntu/trusty/juju-core/trusty-1.22.6 |
|
| 2015-06-29 14:39:21 |
Curtis Hovey |
bug |
|
|
added subscriber Robie Basak |
| 2015-06-29 16:46:34 |
Robie Basak |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-06-29 16:46:34 |
Robie Basak |
bug task added |
|
juju-core (Ubuntu Trusty) |
|
| 2015-06-29 16:57:40 |
Curtis Hovey |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Stable Fix]
[sinzui] Prepare source package, and diffs: TODO
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[<rbasak>] 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] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Stable Fix]
[sinzui] Prepare source package, and diffs: Done
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[<rbasak>] 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] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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 |
|
| 2015-06-29 16:58:47 |
Curtis Hovey |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Stable Fix]
[sinzui] Prepare source package, and diffs: Done
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[<rbasak>] 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] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: TODO
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: Done
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[<rbasak>] 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] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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 |
|
| 2015-06-30 06:30:40 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2015-06-30 06:39:04 |
Launchpad Janitor |
juju-core (Ubuntu): status |
New |
Confirmed |
|
| 2015-06-30 06:39:04 |
Launchpad Janitor |
juju-core (Ubuntu Trusty): status |
New |
Confirmed |
|
| 2015-07-13 13:11:47 |
Curtis Hovey |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: TODO
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: Done
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[<rbasak>] 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] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[<rbasak>] 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] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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 |
|
| 2015-07-15 13:47:23 |
Robie Basak |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[<rbasak>] 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] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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 |
|
| 2015-07-15 13:53:17 |
Robie Basak |
juju-core (Ubuntu): status |
Confirmed |
Fix Committed |
|
| 2015-07-15 13:53:21 |
Robie Basak |
juju-core (Ubuntu Trusty): status |
Confirmed |
In Progress |
|
| 2015-07-15 14:38:17 |
Curtis Hovey |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: TODO
[sinzui] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: TODO
[sinzui] Test juju-deployer against wily-proposed: TODO
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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 |
|
| 2015-07-15 22:22:11 |
Curtis Hovey |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: TODO
[sinzui] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: TODO
[sinzui] Test juju-deployer against wily-proposed: TODO
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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 |
|
| 2015-07-17 14:15:56 |
Chris J Arges |
juju-core (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2015-07-17 14:15:58 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-07-17 14:16:00 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2015-07-17 14:16:07 |
Chris J Arges |
tags |
block-proposed upgrade-software-version |
block-proposed upgrade-software-version verification-needed |
|
| 2015-07-17 14:24:08 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/juju-core |
|
| 2015-07-21 16:15:17 |
Curtis Hovey |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: TODO
[sinzui] Test juju-deployer 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.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE
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-07-21 17:14:44 |
Curtis Hovey |
tags |
block-proposed upgrade-software-version verification-needed |
upgrade-software-version verification-needed |
|
| 2015-07-28 16:27:27 |
Robie Basak |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE
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.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE
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.
[Beret] Landscape team QA: not-needed |
|
| 2015-07-28 16:27:45 |
Curtis Hovey |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE
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.
[Beret] Landscape team QA: not-needed |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE |
|
| 2015-07-28 16:28:50 |
Curtis Hovey |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE
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: NOT NEEDED |
|
| 2015-07-28 16:29:14 |
Curtis Hovey |
tags |
upgrade-software-version verification-needed |
upgrade-software-version verification-done |
|
| 2015-07-28 16:41:50 |
Curtis Hovey |
description |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE
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: NOT NEEDED |
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.
[Devel Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.
[Stable Fix]
[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.
[Pre-QA tasks]
[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE
[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] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE
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.
[Beret] Landscape team QA: not-needed |
|
| 2015-07-28 17:35:18 |
Adam Conrad |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2015-07-28 17:35:15 |
Launchpad Janitor |
juju-core (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-07-30 10:50:35 |
Robie Basak |
juju-core (Ubuntu): status |
Fix Committed |
Fix Released |
|
