| *** akahat|rover is now known as akahat | 05:12 | |
| *** pojadhav- is now known as pojadhav | 05:40 | |
| *** blarnath is now known as d34dh0r53 | 07:01 | |
| *** pojadhav is now known as pojadhav|sick | 11:17 | |
| *** dasm|off is now known as dasm | 14:14 | |
| fungi | tc-members: reminder... the release team wanted to know this week whether adjutant and mistral (probably also zaqar per the discussion in here on sunday) will be sufficiently maintained through the 2023.1 release, or if they should be removed from the release | 14:41 |
|---|---|---|
| fungi | came up again in the release meeting just now | 14:42 |
| gmann | yeah, in discussion with elod. Adjutant is all good to make release soon and Mistral too hopefully but that need more discussion with release team on required things to consider mistral for release. | 18:02 |
| JayF | fungi: gmann: I think part of fungi's question (or am I reading into it?) is about the ability for those projects to be maintained over the life of 2023.1 | 19:05 |
| JayF | hopefully someone has talked to the those folks about it being an 18 month committment? | 19:05 |
| fungi | well, not really, but that's a good thing to consider as well | 19:05 |
| JayF | Ack :) I wasn't sure exactly what was meant by "through the 2023.1 release" | 19:06 |
| fungi | at the moment i'm mainly concerned with whether those projects will be able to produce a release in a few months | 19:06 |
| JayF | I guess you meant process, I was thinking "lifetime of the release" | 19:06 |
| JayF | ack | 19:06 |
| gmann | I am in discussion with both projects maintainer and they are working to make it active | 19:06 |
| gmann | but we cannot take commitment for future right? not even for existing active projects we never know what all be active in next release or so | 19:07 |
| fungi | because we had an almost failure to release in zed with a project that needed release team members to step in and fix stuff which could have caused the release to be either incomplete or late otherwise | 19:07 |
| gmann | we need to keep monitor it cycle by cy;le | 19:07 |
| gmann | Mistral and Adjutant both gate are fixed and PTL/core are ready to make release | 19:07 |
| JayF | gmann: I am just thinking about maintained phase of release... https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases | 19:07 |
| fungi | basically what we don't want is for the release team to be on the hook to fix projects in order to prevent the release from happening | 19:08 |
| JayF | which implies at least to me that letting something in the integrated release is an implicit committment to take bugfixes for those 18 months | 19:08 |
| JayF | but I don't mean to distract from the more immediate issue at hand of the mechanics of the initial release | 19:08 |
| fungi | er, in order to prevent the release from not happening i mean | 19:08 |
| gmann | yeah if they are maintaining/following stable branch things | 19:08 |
| gmann | and it seems none of those are in following stable branch things, at least not in this list https://docs.openstack.org/project-team-guide/stable-branches.html#project-teams-which-asserted-they-follow-the-stable-branch-policy | 19:09 |
| JayF | gmann: awesome; I was hunting for that. Thank you! | 19:09 |
| gmann | for Zaqar, core team know about the issue but yes it is not fixed yet https://review.opendev.org/c/openstack/zaqar/+/857924/comments/a0d5d45e_3008683c they tried switching to different backend https://review.opendev.org/c/openstack/zaqar/+/868975/2 | 19:13 |
| gmann | anyways I am in discussion with release team PTL to figure out the Mistral and Adjutant state before deadline. | 19:14 |
| fungi | thanks! | 19:14 |
| gmann | hopefully both will be able to make release as per current progress but let's see | 19:15 |
| *** dasm is now known as dasm|off | 21:37 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!