| 2015-04-14 15:53:47 |
Oleg Strikov |
bug |
|
|
added bug |
| 2015-04-15 12:50:33 |
Curtis Hovey |
juju-core: status |
New |
Triaged |
|
| 2015-04-15 12:50:35 |
Curtis Hovey |
juju-core: importance |
Undecided |
High |
|
| 2015-04-15 12:50:39 |
Curtis Hovey |
juju-core: assignee |
|
Curtis Hovey (sinzui) |
|
| 2015-04-15 12:51:06 |
Curtis Hovey |
tags |
block-proposed |
block-proposed packaging |
|
| 2015-04-15 16:18:43 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2015-04-15 16:19:51 |
Oleg Strikov |
affects |
juju-core |
juju-core (Ubuntu) |
|
| 2015-04-15 16:23:00 |
Robie Basak |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-04-15 16:23:00 |
Robie Basak |
bug task added |
|
juju-core (Ubuntu Trusty) |
|
| 2015-04-15 16:25:38 |
Oleg Strikov |
juju-core (Ubuntu): assignee |
Curtis Hovey (sinzui) |
|
|
| 2015-04-15 16:25:42 |
Oleg Strikov |
juju-core (Ubuntu): assignee |
|
Oleg Strikov (strikov) |
|
| 2015-04-15 16:25:46 |
Oleg Strikov |
juju-core (Ubuntu Trusty): assignee |
|
Oleg Strikov (strikov) |
|
| 2015-04-15 17:28:33 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/vivid-proposed/juju-core |
|
| 2015-04-15 17:31:59 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2015-04-15 20:08:49 |
Curtis Hovey |
bug |
|
|
added subscriber Curtis Hovey |
| 2015-04-16 13:20:44 |
Curtis Hovey |
information type |
Public |
Private |
|
| 2015-04-16 13:21:41 |
Curtis Hovey |
removed subscriber Nobuto Murata |
|
|
|
| 2015-04-16 13:21:41 |
Curtis Hovey |
removed subscriber Robie Basak |
|
|
|
| 2015-04-16 13:22:22 |
Curtis Hovey |
attachment added |
|
logs from machine 14 https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+attachment/4377157/+files/machine-14.log.xz |
|
| 2015-04-16 13:22:48 |
Curtis Hovey |
attachment removed |
logs from machine 14 https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+attachment/4377157/+files/machine-14.log.xz |
|
|
| 2015-04-16 13:23:15 |
Curtis Hovey |
information type |
Private |
Public |
|
| 2015-04-16 14:38:28 |
Curtis Hovey |
description |
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-proposed, but it should not land in trusty 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. [strikov] 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): TODO
[strikov] 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.1 enter trusty-proposed and vivid-proposed, but it should not land in trusty 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. [strikov] 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): TODO
[strikov] 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: DONE
[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 |
|
| 2015-04-16 15:29:59 |
Curtis Hovey |
description |
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-proposed, but it should not land in trusty 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. [strikov] 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): TODO
[strikov] 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: DONE
[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.1 enter trusty-proposed and vivid-proposed, but it should not land in trusty 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. [strikov] 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): TODO
[strikov] 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: DONE
[sinzui] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: DONE
[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 |
|
| 2015-04-16 15:46:35 |
Oleg Strikov |
description |
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-proposed, but it should not land in trusty 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. [strikov] 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): TODO
[strikov] 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: DONE
[sinzui] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: DONE
[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.1 enter trusty-proposed and vivid-proposed, but it should not land in trusty 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. [strikov] 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
[strikov] 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: DONE
[sinzui] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: DONE
[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 |
|
| 2015-04-16 15:49:23 |
Oleg Strikov |
tags |
block-proposed packaging |
packaging |
|
| 2015-04-16 16:08:14 |
Launchpad Janitor |
juju-core (Ubuntu): status |
Triaged |
Fix Released |
|
| 2015-04-23 14:49:21 |
Robie Basak |
juju-core (Ubuntu Trusty): status |
New |
In Progress |
|
| 2015-05-06 17:44:24 |
Steve Langasek |
juju-core (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2015-05-06 17:44:26 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-05-06 17:44:27 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2015-05-06 17:44:32 |
Steve Langasek |
tags |
packaging |
packaging verification-needed |
|
| 2015-05-08 15:08:58 |
Curtis Hovey |
description |
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-proposed, but it should not land in trusty 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. [strikov] 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
[strikov] 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: DONE
[sinzui] Upstream QA test against Trusty: TODO
[sinzui] Upstream release process complete: TODO
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: DONE
[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.1 enter trusty-proposed and vivid-proposed, but it should not land in trusty 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. [strikov] 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
[strikov] 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: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE
Manual tests required:
[sinzui] Test juju-quickstart against vivid-proposed: DONE
[sinzui] Test juju-quickstart 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-05-08 16:34:44 |
Oleg Strikov |
tags |
packaging verification-needed |
packaging verification-done |
|
| 2015-05-14 14:05:08 |
Oleg Strikov |
tags |
packaging verification-done |
packaging verification-failed |
|
| 2015-05-28 03:12:46 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/juju-core |
|
| 2015-06-01 08:38:52 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2015-06-24 03:20:11 |
Ray Wang |
bug |
|
|
added subscriber Ray Wang |
| 2015-06-30 06:39:04 |
Nobuto Murata |
marked as duplicate |
|
1469744 |
|
| 2015-07-28 17:35:15 |
Launchpad Janitor |
juju-core (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
