Next Zuul release (3.0.1?)
Hi,
We have some mildly-urgent bugfixes merged or ready to merge in Zuul, so I'd like to make a release sometime in the next few days. By mildly-urgent, I mean that the sooner we release the fixes, the less problems people will have in the future (either by creating jobs relying on wrong behavior, or system configurations which are problematic).
The items I have on the list are:
* Roles checkout fix (merged) * Github3.py version bump (ready to merge) * Postgress fixes/support (merging as I write this)
We've also merged some other bugfixes, and may slip some others in during the remaining time. Are there any other items of similar urgency to the three above that we need to release ASAP?
Once we're satisfied (probably tomorrow?) I'll release 3.0.1. I think that since we're only focusing on bugfixes, the micro version bump is appropriate.
I don't think Nodepool needs a corresponding release.
-Jim
On 10.04.18, 16:49, "James E. Blair" corvus@inaugust.com wrote:
Hi,
We have some mildly-urgent bugfixes merged or ready to merge in Zuul, so I'd like to make a release sometime in the next few days. By mildly-urgent, I mean that the sooner we release the fixes, the less problems people will have in the future (either by creating jobs relying on wrong behavior, or system configurations which are problematic).
The items I have on the list are:
* Roles checkout fix (merged) * Github3.py version bump (ready to merge) * Postgress fixes/support (merging as I write this)
We've also merged some other bugfixes, and may slip some others in during the remaining time. Are there any other items of similar urgency to the three above that we need to release ASAP?
Once we're satisfied (probably tomorrow?) I'll release 3.0.1. I think that since we're only focusing on bugfixes, the micro version bump is appropriate.
I don't think Nodepool needs a corresponding release.
-Jim
I think these items (mostly not urgent but small changes/fixes) could be interesting:
https://review.openstack.org/556866 Switch implicit role not found message to debug This fixes misleading log messages which many new users ask about.
https://review.openstack.org/#/c/553702 Don't count non-live queue items in tenant list Small bugfix to the tenant overview
https://review.openstack.org/559745 Fix missing semaphore release on zk error Fixes missing semaphore release during zk instabilities
-Tobias
On Tue, Apr 10, 2018, at 9:50 AM, Tobias.Henkel@bmw.de wrote:
On 10.04.18, 16:49, "James E. Blair" corvus@inaugust.com wrote:
Hi, We have some mildly-urgent bugfixes merged or ready to merge in Zuul, so I'd like to make a release sometime in the next few days. By mildly-urgent, I mean that the sooner we release the fixes, the less problems people will have in the future (either by creating jobs relying on wrong behavior, or system configurations which are problematic). The items I have on the list are: * Roles checkout fix (merged) * Github3.py version bump (ready to merge) * Postgress fixes/support (merging as I write this) We've also merged some other bugfixes, and may slip some others in during the remaining time. Are there any other items of similar urgency to the three above that we need to release ASAP? Once we're satisfied (probably tomorrow?) I'll release 3.0.1. I think that since we're only focusing on bugfixes, the micro version bump is appropriate. I don't think Nodepool needs a corresponding release. -JimI think these items (mostly not urgent but small changes/fixes) could be interesting:
https://review.openstack.org/556866 Switch implicit role not found message to debug This fixes misleading log messages which many new users ask about.
https://review.openstack.org/#/c/553702 Don't count non-live queue items in tenant list Small bugfix to the tenant overview
https://review.openstack.org/559745 Fix missing semaphore release on zk error Fixes missing semaphore release during zk instabilities
-Tobias
As a general thought we should probably be safe to release early and often (say once a week if we want to) since the CI for zuul itself is fairly extensive and we have OpenStack operating as a large canary user. Maybe instead of trying to get everything in for 3.0.1 we just commit to making a 3.0.2 next week and continue from there as necessary to get bug fixes out there door?
My biggest concern with the database related updates is that they can affect new users long term happyness with zuul if things go poorly there. But for most other bugfixes a regular update release cycle should cover them well.
Clark
On Tue, Apr 10, 2018 at 07:48:59AM -0700, James E. Blair wrote:
Hi,
We have some mildly-urgent bugfixes merged or ready to merge in Zuul, so I'd like to make a release sometime in the next few days. By mildly-urgent, I mean that the sooner we release the fixes, the less problems people will have in the future (either by creating jobs relying on wrong behavior, or system configurations which are problematic).
The items I have on the list are:
- Roles checkout fix (merged)
- Github3.py version bump (ready to merge)
- Postgress fixes/support (merging as I write this)
We've also merged some other bugfixes, and may slip some others in during the remaining time. Are there any other items of similar urgency to the three above that we need to release ASAP?
Once we're satisfied (probably tomorrow?) I'll release 3.0.1. I think that since we're only focusing on bugfixes, the micro version bump is appropriate.
I don't think Nodepool needs a corresponding release.
-Jim
I think we may also want to remove zuul-cloner from the 3.0.1 release, we've seen people trying to use it with the 3.0.0 release and it's currently broken.
Paul
participants (4)
-
Clark Boylan
-
corvus＠inaugust.com
-
Paul Belanger
-
Tobias.Henkel＠bmw.de