| *** marios is now known as marios|ruck | 05:14 | |
| *** amoralej|off is now known as amoralej | 07:34 | |
| ttx | JayF: the simplest would probably be for someone with authority to request Ironic releases to kindly ask a release manager to push a tag manually. The open question is what is the best way to request/track the demand? There is little point in pushing an openstack/releases Gerrit change since that will fail tests. Maybe just an IRC message... Maybe an email to the list? | 07:52 |
|---|---|---|
| ttx | Hrm, scratch that -- it looks like https://review.opendev.org/c/openstack/releases/+/860125 is workign as intended since all the bugfixes branches are also stable branches | 07:55 |
| *** marios|ruck is now known as marios | 08:26 | |
| elodilles | as I understand bugfix/<version> branches are there in ironic repos for some time already, and those are cut via yamls in releases repo, however (i guess that was formerly agreed on that) no releases can be produced out of them (as JayF wrote, those are only consumed directly from git). but yes, probably manual releases can be made out of these bugfix branches. though i guess if they become | 09:00 |
| elodilles | frequent requests then relmgmt doesn't want to handle it manually. so this needs some discussion i think | 09:00 |
| ttx | ++ | 09:01 |
| elodilles | also we have a mail thread now about an independent release modeled project that needs (probably) a similar bugfix release as there's no stable branch. the same solution can be done I think: introduce a release process on bugfix branches. the question is though whether we really need this or we should just say that: either consume the latest release or fix an older release 'downstream' | 09:04 |
| elodilles | (i'm talking about this thread: https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030612.html ) | 09:05 |
| *** dviroel|afk is now known as dviroel | 11:30 | |
| *** amoralej is now known as amoralej|lunch | 11:52 | |
| *** amoralej|lunch is now known as amoralej | 13:12 | |
| *** diablo_rojo is now known as Guest2262 | 13:24 | |
| JayF | TBH This is the discussion I was somewhat hoping to start; as well as getting a single manual release done. | 14:10 |
| opendevreview | Jay Faulkner proposed openstack/releases master: Release stable branches from w-y for Ironic projects https://review.opendev.org/c/openstack/releases/+/860125 | 14:32 |
| *** Guest2262 is now known as diablo_rojo | 14:40 | |
| *** dviroel is now known as dviroel|lunch | 14:50 | |
| dmendiza[m] | Hi friends! | 15:07 |
| dmendiza[m] | I was going to ask if lib releases now are zed or antelope, but I don't see an antelope directory in `releasese/deliverables/` | 15:08 |
| elodilles | dmendiza[m]: hi! yepp, antelope releases directory structure will be pushed after the Zed official release | 15:12 |
| dmendiza[m] | gotcha, thanks! | 15:13 |
| *** knikolla[m] is now known as knikolla | 15:18 | |
| clarkb | ttx: elodilles: JayF: if the existing release tooling can support this why wouldn't we do that? It will help avoid releasing invalid versions and ensure that we always tag commits that already exist in the upstream repos. I think that using the tooling if we can will help avoid headaches even beyond the effort to do them manually. | 15:18 |
| *** marios is now known as marios|out | 15:22 | |
| elodilles | clarkb: the tooling allows to create bugfix/<version> branches, but does not allow *releasing* from those branches | 15:24 |
| clarkb | elodilles: I see, that was my confusion then | 15:24 |
| elodilles | the question is whether it is worth to add that functionality (to release from bugfix branches) to our tooling | 15:27 |
| clarkb | right, seems we have ~3 options then. 1) update tooling to do releases from those branches as with stable branches 2) release managers manually do tagging using existing Gerrit ACLs 3) update Gerrit ACLs to allow ironic to push the tags and delegate to them (and technically 4) don't do releases, but it seems there is value there based on jayf's pypi stats) | 15:29 |
| JayF | I think #1 is the best option; but I do not have time to do that work and I don't know if anyone does. | 15:29 |
| JayF | In lieu of that, #2 and #3 are roughly equal to me -- but I think keeping the number of credentials that can trigger a release low does have some value, so I'd lean slightly towards #2 | 15:29 |
| elodilles | about the pypi stats: are those real consumers or CI's pulling the releases for their daily builds o:) | 15:43 |
| elodilles | nevertheless the amount of releases you want to request seems a bit too much to do them manually, i'd say | 15:43 |
| elodilles | so for me #1 or #4 is the real question | 15:44 |
| JayF | elodilles: I did some due dillegence; 6000 downloads over 4 months is well above the "robot noise" threshold | 15:49 |
| elodilles | JayF: ack, i was just curious :) | 15:53 |
| JayF | Yeah I had the same thought as you though for sure | 15:54 |
| JayF | AIUI for an average pypi package, you can expect ~dozens a month just from mirroring | 15:54 |
| JayF | elodilles: after taking it up with contributors, we're going to try and factor out that new dep before doing a release; thanks for bringing it up | 15:58 |
| elodilles | JayF: thanks too for looking after it! | 16:01 |
| JayF | I think I'm learning that PTL actually stands for 'your todo list will never shrink again' :D | 16:02 |
| clarkb | JayF: can confirm. Also condolences | 16:04 |
| elodilles | :D | 16:06 |
| *** dviroel|lunch is now known as dviroel | 16:21 | |
| ianychoi[m] | Hi elodilles , translation jobs for Zed will be enabled once https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/860272 is merged - I processed corresponding version creation on Zanata | 17:00 |
| *** amoralej is now known as amoralej|off | 17:00 | |
| elodilles | ianychoi[m]: thanks! | 17:16 |
| elodilles | ianychoi[m]: and sorry for sending the reminder late for zed :/ | 17:19 |
| *** diablo_rojo is now known as Guest2330 | 18:54 | |
| *** dviroel_ is now known as dviroel|afk | 20:37 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!