Wednesday, 2022-10-19

*** amoralej|off is now known as amoralej07:34
opendevreviewHervĂ© Beraud proposed openstack/releases master: Release oslo' antelope deliverables
opendevreviewStephen Finucane proposed openstack/releases master: stevedore 3.3.3, 3.4.1, 3.5.2, 4.0.2
*** amoralej is now known as amoralej|lunch11:16
opendevreviewMerged openstack/releases master: EOL Rocky for all Ironic-program projects
*** amoralej|lunch is now known as amoralej12:51
opendevreviewMerged openstack/releases master: EOL Stein for all Ironic-program projects
*** ykarel is now known as ykarel|afk15:27
*** dviroel is now known as dviroel|lunch15:46
*** ykarel|afk is now known as ykarel15:48
opendevreviewElod Illes proposed openstack/releases master: Move non-client library freeze to Milestone-2
elodilleshberaud ttx : during the Monday's session 'TC + Community leaders interaction' this was discussed ^^^16:02
elodillesplease review, and if needed we can discuss it in RelMgmt PTG hour16:03
elodilles(it's really just to move nc-lib freeze from ~Milestone3 to Milestone2 to avoid future problems with last minute 'breaking changes' in libraries causing issues for projects - like we had with Sqlalchemy 2.0 compatibility issue (oslo.db 12.1.0) before Zed release)16:06
hberaudmy main concern is that libraries will lose one month of development period, that let us a window of 3 months of active development16:09
elodilleshberaud: yes, i had the same thought16:09
hberaudwith christmas in the middle16:09
elodilleshberaud: clearly from relmgmt viewpoint it's not a problem, but from a library maintainer point of view this is loosing a good amount of development weeks16:10
hberaudmy concern is from an oslo pov16:11
elodillesi guessed that :)16:11
hberaudand also other libs hosted by other teams16:12
elodilles++, of course16:12
hberauddoes the TC socialized this point?16:12
hberaud(on the ML)16:12
elodillesthis was the tc-community leaders interaction session16:12
elodilles* on the16:12
elodillesbut i'll start a thread on ML16:13
hberaudcould be worth16:13
elodillescan you answer there with your concerns?16:13
hberaudI'll speak about that at the next oslo meeting16:13
hberaudsure, I already left a comment16:14
elodilleshberaud: cool, thanks!16:14
hberaudalso we should also notice that usually oslo is frozen before the official date for non client libs16:16
elodilles(i'll send the mail some time after today's PTG sessions, so it won't arrive early today)16:17
hberaudmaybe a compromize could be to add one or two more weeks to this advanced date16:17
elodilleshberaud: hmm, yes, it's not in the schedule yet, but i remember now that it usually happened one week earlier than $nclfreeze16:18
elodillesyes, one or two more weeks could work i think, too16:23
elodilles(the other trivial solution is to ask libraries to release breaking changes as soon as possible in the cycle, but we know that this is theory and in practice... :))16:27
*** dviroel|lunch is now known as dviroel16:28
hberaudyeah sometime the patches are submitted at the begining of a series and merge one or two before the end of the series...16:28
hberaudoslo host a wide range of deliverable and we arn't million of maintainers 16:30
hberaudthe same is true for other teams16:31
elodillesyes, that's true16:32
elodilleshmmm, now i realized my patch is maybe not clear: what was discussed on the 'TC+PTLs' session is rather a 'feature freeze for libraries' than 'a final release'16:34
hberaudI was aware of the *freeze*16:35
hberaudfix can be merged after this date16:35
hberaudbut we lose significant amount of time to develop signficant changes and features16:36
*** amoralej is now known as amoralej|off16:51
elodilleshberaud stephenfin : i've started the mail thread:
elodillesthanks for the comments on the patch so far!17:12
stephenfinelodilles: ty! I'll reply there too :)17:12
elodillesthanks \o/17:13
elodillesand thanks again for the work you did with the fire fighting as well o:)17:14
opendevreviewStephen Finucane proposed openstack/releases master: stevedore 3.3.3, 3.4.2, 3.5.2, 4.0.2
*** dviroel is now known as dviroel|biab20:47
*** dviroel|biab is now known as dviroel21:59
*** dviroel is now known as dviroel|out23:03

Generated by 2.17.3 by Marius Gedminas - find it at!