*** marios is now known as marios|dentist | 06:44 | |
elodilles | fyi, i've proposed yesterday the 1st draft of the Z cycle schedule: https://review.opendev.org/c/openstack/releases/+/824489 | 07:36 |
---|---|---|
elodilles | please let me know if something is wrong with it and i'll update it | 07:37 |
elodilles | generated 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.html | 07:37 |
elodilles | it's a 27 weeks long schedule, i hope it's OK | 07:38 |
*** amoralej|off is now known as amoralej | 07:58 | |
*** mnasiadka_ is now known as mnasiadka | 08:43 | |
opendevreview | Tobias Urdin proposed openstack/releases master: [magnum] [wallaby] Release 12.1.0 https://review.opendev.org/c/openstack/releases/+/824514 | 08:56 |
ykarel | elodilles, hi | 08:57 |
ykarel | elodilles, can you check and confirm if https://etherpad.opendev.org/p/yoga-relmgt-tracking#L197 meeting is right for such queries | 08:57 |
hberaud | ykarel: At first glance I'd argue that's more a topic for the stable team | 09:11 |
hberaud | ykarel: however elodilles is also a member of the stable team so he'll better answer the question than me | 09:12 |
ykarel | hberaud, k Thanks, sure i can move this query to stable team meeting if that's the right place for it | 09:35 |
ykarel | if you have the agenda link handy, please do share | 09:35 |
hberaud | ykarel: let's wait for elodilles's reply first | 09:36 |
hberaud | elodilles: 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 react | 09:38 |
hberaud | usually 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 not | 09:39 |
hberaud | if people react negatively to this one we will be able to create schedule with more or with less weeks | 09:40 |
ykarel | hberaud, elodilles ok Thanks, i am not feeling quite well, so will sign out for today | 09:46 |
ykarel | will check meeting logs and etherpad for updates once i am back | 09:46 |
ykarel | if it's for different meeting i can repropose it | 09:46 |
hberaud | ykarel: oh take care! | 09:47 |
*** ykarel is now known as ykarel|away | 09:47 | |
ykarel|away | just that it's not an urgent one, but just looking for clarity and guidance | 09:47 |
hberaud | ack | 09:47 |
* ykarel|away out | 09:48 | |
elodilles | ykarel (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 |
elodilles | o:)). 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 |
elodilles | complex 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 |
ttx | elodilles: 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 them | 11:15 |
opendevreview | Merged openstack/releases master: Add ansible-collection-kolla deliverable file for Yoga https://review.opendev.org/c/openstack/releases/+/824032 | 11:25 |
opendevreview | Merged openstack/releases master: Release octavia 7.1.2 for victoria https://review.opendev.org/c/openstack/releases/+/824094 | 11:30 |
opendevreview | Merged openstack/releases master: New stable releases for Neutron https://review.opendev.org/c/openstack/releases/+/823779 | 11:35 |
elodilles | ttx: 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 |
elodilles | possible release issues early | 11:36 |
elodilles | anyway, i'll ping kolla and venus teams | 11:37 |
*** amoralej is now known as amoralej|lunch | 13:01 | |
*** amoralej|lunch is now known as amoralej | 14:01 | |
*** akekane_ is now known as abhishekk | 14:29 | |
ttx | it is an option to release only some of them | 14:47 |
ttx | My point is that ideally we should not discover that they are unreleasable on feature freeze day | 14:48 |
ttx | the sooner they exercise the machine the better | 14:48 |
elodilles | yepp, that would be unfortunate :S | 14:48 |
opendevreview | Michael Johnson proposed openstack/releases master: Release oslo.policy 3.7.1 for Wallaby https://review.opendev.org/c/openstack/releases/+/824604 | 16:21 |
opendevreview | Stephen Finucane proposed openstack/releases master: debtcollector 2.4.0 https://review.opendev.org/c/openstack/releases/+/817752 | 18:44 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!