Monday, 2020-11-30

*** tosky has quit IRC00:39
*** ykarel|away has joined #openstack-release04:34
*** ykarel|away has quit IRC04:36
*** ianychoi__ has joined #openstack-release04:57
*** ianychoi_ has quit IRC04:59
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:33
*** brinzhang has joined #openstack-release05:59
*** sboyron has joined #openstack-release06:49
*** whoami-rajat__ has joined #openstack-release07:21
*** slaweq has joined #openstack-release07:27
*** tosky has joined #openstack-release08:37
*** ricolin has quit IRC08:47
*** mgoddard has joined #openstack-release08:55
*** rpittau|afk is now known as rpittau09:27
hberaudttx: o/ around?09:40
ttxyex09:51
hberaudcool09:54
hberaudttx: can you validate these changes ASAP https://review.opendev.org/c/openstack/releases/+/764434 I proposed to move some oslo projects to independent and this is the deadline (W1) so I want to use this patch to ensure that everything is ok and I'll apply the same changes on the other projects on the list => http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018905.html09:56
hberaudThanks09:56
hberaudttx: In parallel I'll propose the cwi-w1 with these projects also included just in case if we won't validate the transition09:58
ttxI'm wondering... Not sure we should rewrite history and remove those releases from past coordinated releases09:59
ttxremove the wallaby file and create an empty independent file, sure10:00
ttxI'm trying to remember past examples of that transition and how we did it10:00
hberaudttx: I copied existing transition10:00
hberaudI wonder too if this is correct, it seems weird to drop history10:01
ttxwhich transition did you copy?10:01
hberaudpbr10:01
hberaudand validations-*10:01
ttxok looking10:02
hberaudbut pbr is an old transition10:02
hberaudand validations-* was a bit different IIRC10:02
ttxyes pbr was a bit of a one-off since IIRC it was released in a coordinated release mostly by accident10:03
ttxI think we should only remove them from past coordinated releases if we consider they should never have been listed there in the first place10:05
ttxwhich is not the case for oslo, where it corresponds to a real transition10:05
ttxIt seems less... destructive to just remove the wallaby file and create a _independent one10:05
ttx(empty)10:06
ttxworst case scenario if we realize it's not the right way to do it, we can move entries over10:06
ttxbut I think it would work10:06
ttxI'll comment on the review in that direction10:07
hberaudI see, thanks10:08
hberaudAlso we have few patches like stevedore, castellan, tooz10:09
hberaudtheir are also in the list10:09
hberaudand they need a release for wallaby10:09
ttxSo those are on the "make independent" list, but have a few patches?10:10
hberaudso I suppose we need 1. to block these patches, 2. apply the transition, 3. copy the new release into the transitioned release10:10
hberaudhttps://review.opendev.org/c/openstack/releases/+/76448110:10
hberaudhttps://review.opendev.org/c/openstack/releases/+/76448010:10
hberaudI think that's all10:10
ttxI'd say we have two options for those10:11
ttx1- Consider it's not a great moment to transition them after all, since they still have changes10:11
ttx(and just keep them in wallaby this cycle)10:11
ttx2- Make them independent AND release those changes as an independent release10:11
hberaudYes, then I think that it could be more safe to keep them in wallaby10:12
hberaudjust in case10:12
ttxMy preference would be... probably (1) since that transition is in theory based on the idea  thatthe lib is stable10:12
hberaudyes10:12
hberaudsame here10:12
ttxNo hurry really10:12
hberaudok10:13
hberaudI'll propose the rest of the list10:13
ttxok, am around for reviews10:13
hberaudand keep (1) for the both10:14
hberaudthanks10:14
openstackgerritHervé Beraud proposed openstack/releases master: Moving oslo projects to independent model  https://review.opendev.org/c/openstack/releases/+/76462410:28
hberaudttx: done ^10:29
hberaudI did a single all-in-one patch10:29
ttxok will check in a minute10:30
hberaudsure np10:38
openstackgerritThierry Carrez proposed openstack/releases master: oslo.metrics 0.1.0 release  https://review.opendev.org/c/openstack/releases/+/76463110:38
ttxLGTM10:39
hberaudttx: OK, so I'll exclude them from c-w-i-w110:45
ttx+110:45
*** mgoddard has quit IRC10:47
*** brinzhang_ has joined #openstack-release10:49
openstackgerritMerged openstack/releases master: python-troveclient 6.0.0 for Wallaby  https://review.opendev.org/c/openstack/releases/+/76444310:51
openstackgerritMerged openstack/releases master: New bugfix release of castellan for train.  https://review.opendev.org/c/openstack/releases/+/76447310:52
*** brinzhang has quit IRC10:53
openstackgerritHervé Beraud proposed openstack/releases master: Moving oslo projects to independent model  https://review.opendev.org/c/openstack/releases/+/76462410:55
hberaudttx: I removed oslo.upgradecheck ^ I missed it was in the same situation as tooz and stevedore10:55
openstackgerritMerged openstack/releases master: New bugfix release of tooz for ussuri.  https://review.opendev.org/c/openstack/releases/+/76447410:57
*** e0ne has joined #openstack-release11:01
*** cgoncalves has quit IRC11:18
*** cgoncalves has joined #openstack-release11:21
*** dtantsur|afk is now known as dtantsur11:31
*** jbadiapa has joined #openstack-release11:40
*** mgoddard has joined #openstack-release11:55
*** mgoddard has quit IRC12:07
*** tosky has quit IRC12:24
*** tosky has joined #openstack-release12:25
*** e0ne has quit IRC13:00
openstackgerritHervé Beraud proposed openstack/releases master: Release automaton for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76466313:10
openstackgerritHervé Beraud proposed openstack/releases master: Release blazar-nova for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76466413:12
openstackgerritHervé Beraud proposed openstack/releases master: Release castellan for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76466513:12
openstackgerritHervé Beraud proposed openstack/releases master: Release ceilometermiddleware for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76466613:13
openstackgerritHervé Beraud proposed openstack/releases master: Release debtcollector for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76466713:13
openstackgerritHervé Beraud proposed openstack/releases master: Release futurist for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76466813:13
openstackgerritHervé Beraud proposed openstack/releases master: Release heat-translator for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76466913:14
openstackgerritHervé Beraud proposed openstack/releases master: Release ironic-lib for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76467013:14
openstackgerritHervé Beraud proposed openstack/releases master: Release keystoneauth for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76467113:15
openstackgerritHervé Beraud proposed openstack/releases master: Release keystonemiddleware for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76467213:15
openstackgerritHervé Beraud proposed openstack/releases master: Release kuryr for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76467313:16
openstackgerritHervé Beraud proposed openstack/releases master: Release metalsmith for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76467413:16
openstackgerritHervé Beraud proposed openstack/releases master: Release mistral-extra for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76467513:16
openstackgerritHervé Beraud proposed openstack/releases master: Release mistral-lib for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76469613:17
openstackgerritHervé Beraud proposed openstack/releases master: Release monasca-common for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76469713:17
openstackgerritHervé Beraud proposed openstack/releases master: Release monasca-statsd for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76469813:18
openstackgerritHervé Beraud proposed openstack/releases master: Release neutron-lib for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76469913:18
openstackgerritHervé Beraud proposed openstack/releases master: Release octavia-lib for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76470013:18
openstackgerritHervé Beraud proposed openstack/releases master: Release os-brick for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76470113:19
openstackgerritHervé Beraud proposed openstack/releases master: Release os-ken for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76470213:20
openstackgerritHervé Beraud proposed openstack/releases master: Release os-vif for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76470313:21
openstackgerritHervé Beraud proposed openstack/releases master: Release os-win for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76470413:22
openstackgerritHervé Beraud proposed openstack/releases master: Release osc-placement for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76470513:23
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.cache for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76470613:24
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.config for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76470713:25
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.context for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76470813:27
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.db for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76470913:28
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.limit for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76471013:28
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.middleware for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76471113:29
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.privsep for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76471213:30
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.serialization for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76471313:30
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.service for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76471413:31
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.versionedobjects for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76471513:32
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.vmware for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76471613:32
openstackgerritHervé Beraud proposed openstack/releases master: Release osprofiler for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76471713:33
openstackgerritHervé Beraud proposed openstack/releases master: Release pycadf for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76471813:33
openstackgerritHervé Beraud proposed openstack/releases master: Release python-adjutantclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76471913:33
openstackgerritHervé Beraud proposed openstack/releases master: Release python-aodhclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76472013:34
openstackgerritHervé Beraud proposed openstack/releases master: Release python-barbicanclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76472113:34
*** armstrong has joined #openstack-release13:35
*** haleyb|away is now known as haleyb13:35
openstackgerritHervé Beraud proposed openstack/releases master: Release python-blazarclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76472213:35
openstackgerritHervé Beraud proposed openstack/releases master: Release python-brick-cinderclient-ext for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76472313:36
openstackgerritHervé Beraud proposed openstack/releases master: Release python-cinderclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76472413:37
openstackgerritHervé Beraud proposed openstack/releases master: Release python-cloudkittyclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76472513:38
openstackgerritHervé Beraud proposed openstack/releases master: Release python-cyborgclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76472613:39
openstackgerritHervé Beraud proposed openstack/releases master: Release python-designateclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76472713:40
openstackgerritHervé Beraud proposed openstack/releases master: Release python-freezerclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76472813:40
openstackgerritHervé Beraud proposed openstack/releases master: Release python-glanceclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76472913:41
openstackgerritHervé Beraud proposed openstack/releases master: Release python-heatclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76473013:41
openstackgerritHervé Beraud proposed openstack/releases master: Release python-ironic-inspector-client for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76473113:42
openstackgerritHervé Beraud proposed openstack/releases master: Release python-ironicclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76473213:43
openstackgerritHervé Beraud proposed openstack/releases master: Release python-keystoneclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76473313:44
openstackgerritHervé Beraud proposed openstack/releases master: Release python-magnumclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76473413:45
openstackgerritHervé Beraud proposed openstack/releases master: Release python-manilaclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76473513:45
openstackgerritHervé Beraud proposed openstack/releases master: Release python-masakariclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76473613:46
openstackgerritHervé Beraud proposed openstack/releases master: Release python-mistralclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76473713:46
openstackgerritHervé Beraud proposed openstack/releases master: Release python-monascaclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76473813:47
openstackgerritHervé Beraud proposed openstack/releases master: Release python-muranoclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76473913:47
openstackgerritHervé Beraud proposed openstack/releases master: Release python-neutronclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76474013:48
openstackgerritHervé Beraud proposed openstack/releases master: Release python-novaclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76474113:48
openstackgerritHervé Beraud proposed openstack/releases master: Release python-octaviaclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76474213:49
openstackgerritHervé Beraud proposed openstack/releases master: Release python-pankoclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76474313:49
openstackgerritHervé Beraud proposed openstack/releases master: Release python-saharaclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76474413:49
openstackgerritHervé Beraud proposed openstack/releases master: Release python-senlinclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76474513:50
openstackgerritHervé Beraud proposed openstack/releases master: Release python-solumclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76474613:51
openstackgerritHervé Beraud proposed openstack/releases master: Release python-swiftclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76474713:51
openstackgerritHervé Beraud proposed openstack/releases master: Release python-tackerclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76474813:51
openstackgerritHervé Beraud proposed openstack/releases master: Release python-vitrageclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76474913:52
openstackgerritHervé Beraud proposed openstack/releases master: Release python-watcherclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76475013:53
openstackgerritHervé Beraud proposed openstack/releases master: Release python-zaqarclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76475113:53
openstackgerritHervé Beraud proposed openstack/releases master: Release python-zunclient for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76475213:53
openstackgerritHervé Beraud proposed openstack/releases master: Release stevedore for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76475313:54
openstackgerritHervé Beraud proposed openstack/releases master: Release sushy-cli for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76475513:55
openstackgerritHervé Beraud proposed openstack/releases master: Release sushy for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76475613:56
openstackgerritHervé Beraud proposed openstack/releases master: Release tooz for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76475713:56
openstackgerritHervé Beraud proposed openstack/releases master: Release tosca-parser for wallaby-1 milestone  https://review.opendev.org/c/openstack/releases/+/76475813:56
*** e0ne has joined #openstack-release13:56
*** redrobot has joined #openstack-release13:59
*** e0ne has quit IRC14:21
amotokihberaud: do we always have to cut a release for wallaby-1 for cycle-with-intermediary model deliverable?14:57
amotokihberaud: I asked it in python-neutronclient release patch https://review.opendev.org/c/openstack/releases/+/764740  and os-ken is almost in the same situation.14:57
*** e0ne has joined #openstack-release14:59
hberaudamotoki: o/ Good question, the documentation isn't crystal clear about this but implicitly I suppose that we could answer "yes we have to cut" to your question, ttx any opinion?15:07
hberaud^15:07
amotokihberaud: do you mean only victoria to wallaby transition mechanical patch is a feature enough? I am okay if the release team hopes such mechanical change as a release.15:09
smcginnisWe should not be doing releases for things that are only CI configuration.15:13
smcginnisWe really only want to get a release out if there are actual changes for consumers to pick up.15:13
smcginnisRegarding switches to independent - those should only remove the Wallaby deliverable files. The older cycle-based releases should stay in place.15:15
hberaudsmcginnis: ack, thanks for your confirmation15:15
hberaudamotoki: ^ so this isn't mandatory15:16
smcginnisWe really do these automatic proposals to make sure teams aren't accumulating changes and not thinking about releasing them until close to the end of the cycle.15:18
smcginnisThen there's less time and a larger number of changes, so the risk is higher that something will cause unintended side effects.15:18
hberaudI see, make sense15:19
smcginnisAnd it will be harder to track down what specific change caused the problem, with limited time to stabilize things as the end of the cycle is approaching.15:19
ttx+1 to what smcginnis said15:19
amotokismcginnis: yeah, I understand it and it totally makes sense.15:19
ttxwould probably be good to drop some of those patches based on that15:19
hberaudyep15:19
smcginnisPlus we still really want to make sure teams get two releases out there during the cycle so we know whether they will have something for this cycle or not.15:19
amotokia release patch is a good trigger to check whether a team should cut a release not :-)15:20
hberaud:)15:20
smcginnisIt does help as a reminder. But only when there are actual changes to be released.15:20
smcginnisHmm, looks like the new gerrit doesn't like how many queries are in the dashboard. :/15:21
ttxyeah, I simplified the dashboard15:23
ttx(I mean mine)15:23
ttxbecause there is a hard limit at 1015:23
ttxBUT that limit is not new15:23
ttxSo I suspect it's just due to us updating it for Wallaby15:24
ttxhttps://gerrit.googlesource.com/gerrit/+blame/refs/heads/master/java/com/google/gerrit/server/restapi/change/QueryChanges.java#16215:24
smcginnisYeah, looks like the generated one in the docs that dropped stein works.15:26
*** armax has joined #openstack-release15:32
smcginnisttx: I see where the problem is in check-release-approval for PTL-less teams. You don't have a change up for that already, right?15:32
ttxno15:34
smcginnisGreat, change coming then.15:34
*** e0ne has quit IRC15:38
*** brinzhang0 has joined #openstack-release15:55
*** brinzhang_ has quit IRC15:58
openstackgerritMerged openstack/releases master: New bugfix release of tooz for wallaby.  https://review.opendev.org/c/openstack/releases/+/76448115:58
TheJuliaQuestion for stable minded folks. We like a couple other projects still backport and try to merge fixes to EM branches, in this case queens. Is there any perceived issue with skipping any back-ports on the other em branches and just landing on the desired em branch?16:01
smcginnisMaybe a question for #openstack-stable, but the venn diagram for the stable team is kind of a bull's eye at this point I guess.16:02
smcginnisIdeally I would think it should still go to each branch. There's a risk someone could upgrade from one EM branch to a more recent one and get a regression.16:03
smcginnisProbably a very low risk though.16:03
smcginniselod: Any thoughts? ^^16:03
TheJuliaThese sorts of things are highly targetted and if we don't skip then we're basically adding 1-4 weeks of delay and work unless we just stip all testing off the EM branches we don't care about16:04
smcginnisSince there won't be any official releases containing these fixes, that's probably safe to do. If someone actually does want to upgrade from one EM release to another, they will need to be manually pulling in fixes anyone.16:05
smcginnisProbably not too burdensome to have to pull in a fix from another branch if needed.16:06
TheJuliayeah16:12
elodsmcginnis TheJulia : well, according to stable policy, to skip a branch is not an option, and I would not recommend either. imagine that someone uses a different EM branch than you are backporting to (e.g. rocky). so this could be confusing16:13
TheJuliaI just feel like there will be resistance to nuking em-branch testing except for the branch we want testing workin on16:13
TheJuliaelod: Perhaps stable policy needs to be revisited? I'e seen this pattern a couple times before, and it came up during ironic's PTG so we wanted to clarify the take on such16:14
elodalso If a patch is fixed on master and newer branches, and the patch is working in older EM branch, then I don't see why it should not merge in time in less older branches16:14
TheJuliaKeeping CI working on older branches has sunk human months of my time in the past couple of years16:15
TheJuliait is an endless battle.16:15
elodTheJulia: I remember the discussion @ Shanghai16:15
elodbut I don't remember what was the exact end of the discussion, to be honest :)16:16
elodTheJulia: I completely understand. I feel like if we are fixing the CI branch-by-branch is not that greater burden than to fix it on a (very) old EM branch16:17
*** brinzhang0 has quit IRC16:18
elodjust fixing the (very) old EM branch is also a big burden itself, I mean16:18
TheJuliaUnfortunately it is often one offs from the evolution of testing and the performance variation that seems to shoot us in the foot16:19
*** brinzhang0 has joined #openstack-release16:19
TheJuliayeah16:19
-openstackstatus- NOTICE: The Gerrit service on review.opendev.org is being restarted quickly to troubleshoot high load and poor query caching performance, downtime should be less than 5 minutes16:21
elodby skipping maintaining specific EM branches means (as I understand) some kind of an LTS, where the whole Extended Maintenance discussion started and introduced as a more feasible solution16:22
elodaround beginning of 201816:23
elod(and waaaay before that afaik)16:23
smcginnisThat's a good point elod. This really is an LTS versus EM discussion. And at least last time it was discussed, the community did not want to support LTS.16:25
elodTheJulia: if I can help with my reviews to speed up backporting to EM branches, then let me know, add me as a reviewer and I'll try to help :)16:26
elodsmcginnis: yes, at least that was the resolution, that community does not want and cannot support an LTS process.16:30
TheJuliathe community as a whole, but some of us responsible for things downstream still need the upstream tests upfront to be good16:34
elodthat's true16:38
elodbut again, I think it's a very rare case, when a CI works well in e.g. back till stein, and does not work in rocky, but still works in queens. so usually if CI on rocky is broken, then queens has the very same issue (plus others)16:42
*** e0ne has joined #openstack-release16:45
*** e0ne has quit IRC16:51
*** e0ne has joined #openstack-release17:21
smcginnishberaud: Did you want to continue to do single core approvals for the current series releases? Or require two cores like we do for stable releases?17:22
*** e0ne has quit IRC17:25
*** e0ne has joined #openstack-release17:29
*** mgoddard has joined #openstack-release17:30
*** mgoddard has quit IRC17:35
*** rpittau is now known as rpittau|afk17:42
*** e0ne has quit IRC17:42
openstackgerritMerged openstack/releases master: Retiring the Qinling's projects  https://review.opendev.org/c/openstack/releases/+/76443917:43
openstackgerritMerged openstack/releases master: Retiring the Searchllight's projects  https://review.opendev.org/c/openstack/releases/+/76444017:46
openstackgerritMerged openstack/releases master: Retiring the Karbor's projects  https://review.opendev.org/c/openstack/releases/+/76443817:46
openstackgerritMerged openstack/releases master: New feature release of stevedore for wallaby.  https://review.opendev.org/c/openstack/releases/+/76448017:47
*** dtantsur is now known as dtantsur|afk18:13
*** dave-mccowan has quit IRC18:36
*** dave-mccowan has joined #openstack-release18:42
hberaudsmcginnis: If possible I prefer two cores validations if no we aren't in hurry18:48
hberaudthe double checks are more safe18:51
smcginnisOK, sounds good.18:52
hberaudsmcginnis: do you think about something?18:53
*** mgoddard has joined #openstack-release19:19
*** mgoddard has quit IRC19:33
*** tosky has quit IRC19:45
smcginnishberaud: Sorry, what was that?19:49
*** dave-mccowan has quit IRC19:59
*** dave-mccowan has joined #openstack-release20:02
hberaudsmcginnis: I was thinking that you thinking about something related to the "two cores requires" and that you wanted to propose something. I surely supposed too much :)20:26
hberauds/that you thinking/that you was thinking/20:27
*** tosky has joined #openstack-release20:48
*** sboyron has quit IRC20:54
*** sboyron has joined #openstack-release20:56
*** whoami-rajat__ has quit IRC21:08
smcginnishberaud: Oh, no. Just seeing if you wanted to keep things with the single core or do two cores instead since I noticed you usually didn't single approve.22:24
smcginnisMeant to bring it up in a meeting so you could officially make the policy change, but since there's just a few of us, probably no need to. The statement above is probably enough.22:26
-openstackstatus- NOTICE: The Gerrit service on review.opendev.org is being restarted quickly to make further query caching and Git garbage collection adjustments, downtime should be less than 5 minutes22:37
*** slaweq has quit IRC22:40
*** slaweq has joined #openstack-release22:45
*** slaweq has quit IRC22:50
*** armstrong has quit IRC23:04
*** tkajinam has quit IRC23:10
*** tkajinam has joined #openstack-release23:11
*** jbadiapa has quit IRC23:15

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!