Thursday, 2022-01-13

*** marios is now known as marios|dentist06:44
elodillesfyi, i've proposed yesterday the 1st draft of the Z cycle schedule: https://review.opendev.org/c/openstack/releases/+/82448907:36
elodillesplease let me know if something is wrong with it and i'll update it07:37
elodillesgenerated page can be seen here: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_bfd/824489/1/check/openstack-tox-docs/bfdf48a/docs/zen/schedule.html07:37
elodillesit's a 27 weeks long schedule, i hope it's OK07:38
*** amoralej|off is now known as amoralej07:58
*** mnasiadka_ is now known as mnasiadka08:43
opendevreviewTobias Urdin proposed openstack/releases master: [magnum] [wallaby] Release 12.1.0  https://review.opendev.org/c/openstack/releases/+/82451408:56
ykarelelodilles, hi08:57
ykarelelodilles, can you check and confirm if https://etherpad.opendev.org/p/yoga-relmgt-tracking#L197 meeting is right for such queries08:57
hberaudykarel: At first glance I'd argue that's more a topic for the stable team09:11
hberaudykarel: however elodilles is also a member of the stable team so he'll better answer the question than me09:12
ykarelhberaud, k Thanks, sure i can move this query to stable team meeting if that's the right place for it09:35
ykarelif you have the agenda link handy, please do share09:35
hberaudykarel: let's wait for elodilles's reply first09:36
hberaudelodilles: thanks for the Z cycle schedule. I'd suggest to send a mail on our ML to highlight this patch and allowing distros maintainer to react09:38
hberaudusually the pain point is the proposed number of week so at this point we are able to see if 27 weeks is an issue or not09:39
hberaudif people react negatively to this one we will be able to create schedule with more or with less weeks09:40
ykarelhberaud, elodilles ok Thanks, i am not feeling quite well, so will sign out for today09:46
ykarelwill check meeting logs and etherpad for updates once i am back09:46
ykarelif it's for different meeting i can repropose it09:46
hberaudykarel: oh take care!09:47
*** ykarel is now known as ykarel|away09:47
ykarel|awayjust that it's not an urgent one, but just looking for clarity and guidance09:47
hberaudack09:47
* ykarel|away out09:48
elodillesykarel (answering here, as maybe you read the channel logs later on): first of all, get well soon! about the issue: well, this is only loosely related to release management topics, rather stable maintenance. however, for a long time, there is no such a meeting for stable maintenance group (especially as there are currently me + release managers who have stable-maint group membership only 10:54
elodilleso:)). similar issue like you mentioned rises time to time. the usual answer is that we should avoid requirements bumping in stable branches (for lower constraints job fixes these were a bit different as it turned out the job worked wrongly and there were lots of conflicts that didn't even work, so it was kind of necessary to fix (some team simply dropped their l-c job)). anyway, this is a bit 10:54
elodillescomplex question, i think if it is really necessary, then lc bumps can be the exceptions, though every case needs to be considered thoroughly and separately. i'll try to drop a mail to the ML in this topic as well.10:54
ttxelodilles: for all those late-added deliverables it would be great if they could do a release very soon, so that we fix any release jobs failures for them11:15
opendevreviewMerged openstack/releases master: Add ansible-collection-kolla deliverable file for Yoga  https://review.opendev.org/c/openstack/releases/+/82403211:25
opendevreviewMerged openstack/releases master: Release octavia 7.1.2 for victoria  https://review.opendev.org/c/openstack/releases/+/82409411:30
opendevreviewMerged openstack/releases master: New stable releases for Neutron  https://review.opendev.org/c/openstack/releases/+/82377911:35
elodillesttx: as far as i understand venus is still struggling with some ci issues so for them (maybe) will be hard to release anything. btw, they have 4 different deliverables (marked now as 'cycle-with-rc' but i guess some could/should be cycle-with-intermediary), do we need all 4 to be released ASAP or is that an option to release only some of them? I guess we need to release all 4 to catch all 11:36
elodillespossible release issues early11:36
elodillesanyway, i'll ping kolla and venus teams11:37
*** amoralej is now known as amoralej|lunch13:01
*** amoralej|lunch is now known as amoralej14:01
*** akekane_ is now known as abhishekk14:29
ttxit is an option to release only some of them14:47
ttxMy point is that ideally we should not discover that they are unreleasable on feature freeze day14:48
ttxthe sooner they exercise the machine the better14:48
elodillesyepp, that would be unfortunate :S14:48
opendevreviewMichael Johnson proposed openstack/releases master: Release oslo.policy 3.7.1 for Wallaby  https://review.opendev.org/c/openstack/releases/+/82460416:21
opendevreviewStephen Finucane proposed openstack/releases master: debtcollector 2.4.0  https://review.opendev.org/c/openstack/releases/+/81775218:44

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