[Bug 1940858] Re: [SRU] python-oslo.messaging stable point release
Corey Bryant
1940858 at bugs.launchpad.net
Mon Aug 23 19:24:44 UTC 2021
** Description changed:
[Impact]
- This release sports mostly bug-fixes and we would like to make sure all of our
- users have access to these improvements.
+ This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements.
The update contains the following package updates:
- * focal: python-oslo.messaging 12.1.6
- * victoria: python-oslo.messaging 12.5.2
- * hirsute: python-oslo.messaging 12.7.1
+ * focal: python-oslo.messaging 12.1.6
+ * victoria: python-oslo.messaging 12.5.2
+ * hirsute: python-oslo.messaging 12.7.1
[Test Case]
The following SRU process was followed:
- https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates
+ https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates, in addition to the documented "New upstream microreleases" section from https://wiki.ubuntu.com/StableReleaseUpdates.
- In order to avoid regression of existing consumers, the OpenStack team will
- run their continuous integration test against the packages that are in
- -proposed. A successful run of all available tests will be required before the
- proposed packages can be let into -updates.
+ In order to avoid regression of existing consumers, the OpenStack team
+ will run their continuous integration test against the packages that are
+ in -proposed. A successful run of all available tests will be required
+ before the proposed packages can be let into -updates.
- The OpenStack team will be in charge of attaching the output summary of the
- executed tests. The OpenStack team members will not mark ‘verification-done’ until
- this has happened.
+ The OpenStack team will be in charge of attaching the output summary of
+ the executed tests. The OpenStack team members will not mark
+ ‘verification-done’ until this has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned tests are attached to this bug.
[Discussion]
** Also affects: oslo.messaging
Importance: Undecided
Status: New
** No longer affects: oslo.messaging
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Also affects: cloud-archive/wallaby
Importance: Undecided
Status: New
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Changed in: cloud-archive/ussuri
Status: New => Triaged
** Changed in: cloud-archive/victoria
Status: New => Triaged
** Changed in: cloud-archive/wallaby
Status: New => Triaged
** Changed in: cloud-archive/wallaby
Importance: Undecided => High
** Changed in: cloud-archive/victoria
Importance: Undecided => High
** Changed in: cloud-archive/ussuri
Importance: Undecided => High
** Changed in: cloud-archive
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to python-oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1940858
Title:
[SRU] python-oslo.messaging stable point release
Status in Ubuntu Cloud Archive:
Invalid
Status in Ubuntu Cloud Archive ussuri series:
Triaged
Status in Ubuntu Cloud Archive victoria series:
Triaged
Status in Ubuntu Cloud Archive wallaby series:
Triaged
Status in python-oslo.messaging package in Ubuntu:
Invalid
Status in python-oslo.messaging source package in Focal:
Triaged
Status in python-oslo.messaging source package in Hirsute:
Triaged
Bug description:
[Impact]
This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements.
The update contains the following package updates:
* focal: python-oslo.messaging 12.1.6
* victoria: python-oslo.messaging 12.5.2
* hirsute: python-oslo.messaging 12.7.1
[Test Case]
The following SRU process was followed:
https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates, in addition to the documented "New upstream microreleases" section from https://wiki.ubuntu.com/StableReleaseUpdates.
In order to avoid regression of existing consumers, the OpenStack team
will run their continuous integration test against the packages that
are in -proposed. A successful run of all available tests will be
required before the proposed packages can be let into -updates.
The OpenStack team will be in charge of attaching the output summary
of the executed tests. The OpenStack team members will not mark
‘verification-done’ until this has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned tests are attached to this bug.
[Discussion]
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1940858/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list