| *** marios is now known as marios|ruck | 06:05 | |
| opendevreview | Dr. Jens Harbott proposed openstack/releases master: Tag monthly kolla stable releases https://review.opendev.org/c/openstack/releases/+/866961 | 07:24 |
|---|---|---|
| *** dviroel|afk is now known as dviroel | 10:51 | |
| opendevreview | Merged openstack/releases master: Release Tempest 33.0.0 as end of support for W https://review.opendev.org/c/openstack/releases/+/866857 | 12:22 |
| opendevreview | Rico Lin proposed openstack/releases master: Release Magnum stable branches https://review.opendev.org/c/openstack/releases/+/866877 | 12:26 |
| ttx | fungi: yes we'll likely have to bring it up... we traditionally require things to be in or out by milestone-2, which serves as a check that the release jobs are all set | 14:04 |
| ttx | so a last minute decision is not so great | 14:04 |
| ttx | cc: elodilles and hberaud | 14:04 |
| fungi | https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-07-16.00.log.html#l-27 | 14:06 |
| fungi | there was some side-channel discussion there, though the meeting was in zoom (i think a transcript will be published soonish) | 14:06 |
| opendevreview | Bartosz Bezak proposed openstack/releases master: [kolla] Release kolla for Zed and cut branch https://review.opendev.org/c/openstack/releases/+/864508 | 14:07 |
| fungi | https://review.opendev.org/c/openstack/governance/+/849153 | 14:07 |
| fungi | is the change marking it inactive for now | 14:08 |
| opendevreview | Merged openstack/releases master: [monasca] Transition Queens to End of Life https://review.opendev.org/c/openstack/releases/+/865757 | 14:08 |
| opendevreview | Michal Nasiadka proposed openstack/releases master: [kolla] Release ansible-collection-kolla for Zed and cut branch https://review.opendev.org/c/openstack/releases/+/864505 | 14:11 |
| opendevreview | Bartosz Bezak proposed openstack/releases master: [kolla] Release ansible-collection-kolla for Zed and cut branch https://review.opendev.org/c/openstack/releases/+/864505 | 14:29 |
| opendevreview | Bartosz Bezak proposed openstack/releases master: [kolla] Release kolla-ansible for Zed and cut branch https://review.opendev.org/c/openstack/releases/+/864507 | 14:37 |
| mnasiadka | Most of the Kolla deliverables (except Kayobe) are ready for branching, we plan branching Kayobe next week. | 14:55 |
| elodilles | mnasiadka: ack, thanks for the info. note that next week is the planned deadline for trailing projects' zed final release | 14:58 |
| elodilles | (usually branch cutting happens earlier than the final release, to have some code freeze, code settling period) | 14:59 |
| elodilles | ttx: ack, thanks for the info | 14:59 |
| elodilles | this means when the governance patch merges we need to remove adjutant repos from deliverables/antelope/, right? ( https://review.opendev.org/c/openstack/governance/+/849153 ) | 15:01 |
| mnasiadka | elodilles: we're aware, but had problems with getting in EL9 support on time | 15:08 |
| elodilles | mnasiadka: ack | 15:22 |
| *** ykarel_ is now known as ykarel|away | 15:47 | |
| ttx | elodilles: well if it could be re-added at the last minute I don't know... I think we should ask them to make a final call before milestone-2 | 15:52 |
| fungi | elodilles: yes, adjutant ceases to be an expected part of the coordinated release if 849153 is approved, but gmann said he told the adjutant ptl it could still be added back to the release if the project still looks okay. sounds like that decision will have to be made no later than milestone 2 which is four weeks away | 15:52 |
| ttx | other options are kinda disruptive to our process | 15:53 |
| fungi | it's so far into the cycle already that at this point the tc really should just be deciding whether adjutant is in or out for 2023.1, there's not much time left to re-add them if they're removed now | 15:54 |
| fungi | probably better to set the expectation with the ptl that adjutant could be added back for the 2023.2 release if things still look good by milestone 2 of that cycle | 15:55 |
| *** dviroel is now known as dviroel|lunch | 16:10 | |
| *** marios|ruck is now known as marios|out | 16:39 | |
| elodilles | oh, i see. well, the entry level is not that hard, we just need a working gate o:) but for that we need maintainers to look at the state of the repositories (all that belong to adjutant team) time to time, and this is what fails usually with low-activity projects :/ | 16:45 |
| elodilles | but yes, from rel-mgmt perspective, the best is to have the decision (in or out) before Antelope-2 | 16:49 |
| elodilles | and 2023.2 is a safer bet, i agree | 16:49 |
| *** dviroel|lunch is now known as dviroel | 17:06 | |
| gmann | elodilles: fungi for adjutant, as it is in release we do not need to change anything now. step from TC on inactive project marking will be 1. mark project inactive 2. monitor/check the situation before final release 3. a) if no change in situation then NO final release for that cycle OR b) if they become active then they can release it 4. in next cycle TC discuss about retirement | 18:32 |
| gmann | for adjutant, PTL has already fixed the gate and he is on top of making other changes merged also | 18:32 |
| gmann | elodilles: fungi : ttx: as adjutant is with 'cycle-with-rc' model this ^^ should work right? let me know if release team wanted any change in that to avoid last min surprise/extra-work ? | 18:34 |
| fungi | gmann: from what i understand, either we need to know in the next 4 weeks whether it will be in the release or not. we can't "wait and see" any longer than that | 18:47 |
| gmann | elodilles: and mistral seems getting more contributors so I am hoping situation will be good there but let's see how it goes | 18:48 |
| fungi | so 4 weeks from now, at milestone 2, if adjutant is in good shape to be released and its contributors can commit to keeping it in shape through the release date, then it can be included | 18:48 |
| gmann | fungi: you mean final list of release deliverables list has to be decided by m-2 ? even for 'cycle-with-rc' ? | 18:48 |
| fungi | that's my understanding of the release process, yes | 18:49 |
| fungi | things got changed up after milestone 2 last cycle, and that caused a lot of problems and scramble | 18:49 |
| fungi | which is why i strongly encouraged you to check with the release team before asserting to the adjutant ptl that it would be okay to decide later in the cycle | 18:50 |
| gmann | well that is not about adjutant only then we need to change process for inactive project timeline | 18:51 |
| fungi | and i thought you indicated to me in #openstack-tc that you had done so, but it's possible i misunderstood | 18:51 |
| gmann | I agree to decide the things by m-2 and not leave for last minute | 18:51 |
| fungi | anyway, i just wanted to make sure the tc and release managers were talking about this as soon as possible so that everyone's on the same page and has the same expectations | 18:52 |
| gmann | let me make the timeline for inactive project to be m-2 not the final release- https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#timeline | 18:52 |
| gmann | I will propose the change to the timeline which will applicable to the all projects entering as Inactive. Adjutant is in good shape as PTL started working and fixed the gate too but we can more monitor it till m-2 | 18:54 |
| gmann | Adjutant is going to be the first project entering the Inactive list so it is good we are verifying the timeline before we are doing it | 18:55 |
| *** dviroel_ is now known as dviroel | 19:17 | |
| *** dviroel is now known as dviroel|afk | 20:20 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!