| slaweq | hi, can you maybe help me with one question about project from the x/ namespace, exactly about whitebox-neutron-tempest-plugin? I know that it is not part of the official release and release team is not doing anything to make releases of it. We can push tag when needed but I don't know what we are missing to be able to publish tarballs in https://tarballs.opendev.org/x/whitebox-neutron-tempest-plugin/ | 06:36 |
|---|---|---|
| elodilles | slaweq: good question. tagging and pypi releasing can be done by the person who is added as maintainer on pypi, as far as i know, but i'm not aware of whether such releases got uploaded ever under tarballs.opendev.org | 07:18 |
| elodilles | i guess it needs manual upload and with that i think infra team can help | 07:18 |
| elodilles | release-team: ^^^ do you have any knowledge / memory about slaweq's question? | 07:19 |
| elodilles | i remember that lajoskatona did some release maybe on tap-as-a-service back in time, when it was under x/ :) maybe he remembers :) | 07:20 |
| slaweq | elodilles I was asking because I see that it is done e.g. for tobiko project https://tarballs.opendev.org/x/tobiko/ so it is definitely doable but I have no idea how :/ | 07:22 |
| elodilles | slaweq: i don't know how tobiko's maintainers do it ( https://pypi.org/project/tobiko/ ; plus there is openstackci as well as maintainer :-o so maybe it's via the CI somehow?) :/ | 07:27 |
| elodilles | slaweq: actually, somehow the CI is triggered, as for example a former release triggered this 'release-job-failures' mail: https://lists.openstack.org/archives/list/release-job-failures@lists.openstack.org/message/DFPKV6EGESFWSL2DQ726AJP7TWSV47NX/ | 07:30 |
| ttx | slaweq: you should be able to manually push tags, and then have Zuul jobs that react to that tagging and build and upload tarballs | 07:35 |
| ttx | You basically need the jobs in the second part of https://releases.openstack.org/reference/release_infra.html | 07:36 |
| ttx | (my yearly reminder that I'm so happy I took the time to document the process in this doc) | 07:38 |
| elodilles | :) | 07:38 |
| frickler | tobiko is using the publish-to-pypi project-template, which IMO should only be used by openstack projects | 07:43 |
| frickler | so we might need to discuss this with the TC maybe | 07:44 |
| frickler | to avoid this being misinterpreted as some official deliverable | 07:44 |
| frickler | although the current docs do not mention such a restriction, hmm https://docs.opendev.org/opendev/infra-manual/latest/drivers.html#tagging-a-release | 07:48 |
| slaweq | thx a lot | 07:57 |
| slaweq | ttx elodilles frickler I found job publish-openstack-artifacts in https://opendev.org/openstack/project-config/src/commit/e14c4fbf962f0d98c066c3435943317cf1bdc446/zuul.d/jobs.yaml#L7 and it seems to be sending tarballs to the server but it seems to be only for the official projects, or should I use the same one for project from x/ namespace too? | 08:06 |
| frickler | slaweq: see my comments in #openstack-tc, I would suggest to wait on some feedback on that first | 08:10 |
| slaweq | @frickler yeah, I saw them already | 09:04 |
| frickler | elodilles: would you agree to abandon the tripleo eom patch? https://review.opendev.org/c/openstack/releases/+/910395 I'll push forward on retiring the remaining repo next week | 09:08 |
| frickler | elodilles: I also saw you were abandoning some stable branch patches yesterday, shall we approve the two remaining patches and then run the branch cleanup? | 09:09 |
| elodilles | frickler: tripleo: you can use the existing patch or create a new that EOLs the branches, whichever suits you better. thanks in advance! | 09:30 |
| elodilles | frickler: yepp, if the remaining EOM/EOL xwv patches are OK to merge then we can do that. I can run the branch delete script after (or maybe early next week). | 09:32 |
| elodilles | and thanks for helping all with these frickler o/ | 09:33 |
| frickler | elodilles: the idea for tripleo was to neither EOM nor EOL if the whole project is retired, similar like we didn't touch other retired projects at all | 10:11 |
| elodilles | frickler: oh, sorry, i misunderstood then. i think retired projects, where we have stable/<series> branch, should be EOL'd. otherwise we got pings time to time that why are those branches open o:) (as we only delete branches when we EOL them (or transition to Unmaintianed)) | 11:12 |
| elodilles | (so i thought that 'marking them retired' is a parallel thing o:)) | 11:32 |
| frickler | elodilles: hmm, ok, I don't actually mind doing that, but we might also want to check a lot of other repos, then, like the recently retired openstack-chef stack | 11:41 |
| frickler | but then I'll amend your patch to eol things | 11:41 |
| opendevreview | Merged openstack/releases master: [OpenStackAnsible] Transition EM branches to Unmaintained https://review.opendev.org/c/openstack/releases/+/910414 | 11:50 |
| elodilles | frickler: openstack-chef is a bit different because it is not part of the recent official deliveries, afair | 11:51 |
| frickler | elodilles: well tripleo also hasn't been for a bit? | 11:52 |
| elodilles | frickler: yepp, but tripleo has open wallaby branches as it was released at that time | 12:09 |
| elodilles | so best is to EOL those branches | 12:10 |
| elodilles | IMO | 12:10 |
| opendevreview | Merged openstack/releases master: [Puppet OpenStack] Transition EM branches to Unmaintained https://review.opendev.org/c/openstack/releases/+/910408 | 12:18 |
| frickler | elodilles: while checking tripleo things, I notice that a lot of them also have stable/zed branches, but those aren't listed in any deliverables file, do you know something about that? shall we just ignore them? (cc gmann) | 12:29 |
| elodilles | :-o | 12:29 |
| elodilles | yeah, i see, this is why we have them: https://review.opendev.org/c/openstack/releases/+/863011 | 12:36 |
| elodilles | it was a weird situation, and we probably shouldn't allow that, but meh... | 12:37 |
| frickler | oh, I didn't check that, nice. but then I think I can create a patch to those to create zed-eol tags that should allow cleanup of those branches | 12:41 |
| elodilles | well, good question whether release tools will like them, fingers crossed :) | 12:43 |
| opendevreview | Thierry Carrez proposed openstack/releases master: Fix erroneous dates in schedule details https://review.opendev.org/c/openstack/releases/+/915707 | 12:53 |
| frickler | not sure what went wrong here for the puppet-eom patch? https://zuul.opendev.org/t/openstack/build/ce80cca2374d4a6d9af88caa9cf3dcbb | 13:39 |
| elodilles | frickler: neither see i the problem... checked random tags and branches and seemed to be there | 13:59 |
| elodilles | let's start the RelMgt PTG session o/ | 14:01 |
| opendevreview | David Wilde proposed openstack/releases master: Create new keystone-tempest-plugin release for 2024.1 https://review.opendev.org/c/openstack/releases/+/915713 | 14:08 |
| frickler | found the errors in the middle of the job output: https://paste.opendev.org/show/bwEGLvqKZPE6LC1YU2zs/ | 14:46 |
| frickler | seems those are the retired repos | 14:46 |
| elodilles | yepp. but those should be EOL'd and no need for unmaintained/* branches O.o | 14:47 |
| tkajinam | yeah... this is just bad timing. I proposed retirement some time ago which got stuck for some time, but it was merged just before that unmaintained transition was merged | 15:21 |
| tkajinam | we can EOL wallaby/xena of these repos and also yoga | 15:21 |
| frickler | tkajinam: yes, I didn't check that patch closely enough, but I also think that maybe the gate check should have caught that issue | 15:33 |
| frickler | I also think that with the current retirement acl being in place, we might get the same error on trying to push eol tags, too. but we can try that | 15:34 |
| elodilles | tkajinam frickler : note that i've updated the patch to EOL those before we approved it: https://review.opendev.org/c/openstack/releases/+/910408 | 15:41 |
| elodilles | (hmmm, it seems not all was EOL'd... my bad than) | 15:42 |
| tkajinam | elodilles, the problem is that a few more was EOLed after your update | 15:43 |
| elodilles | ACK | 15:43 |
| opendevreview | David Wilde proposed openstack/releases master: Create new keystone-tempest-plugin release for 2023.2 https://review.opendev.org/c/openstack/releases/+/915745 | 16:33 |
| opendevreview | Takashi Kajinami proposed openstack/releases master: [Puppet OpenStack] EOL unmaintained branches of retired modules https://review.opendev.org/c/openstack/releases/+/915746 | 16:35 |
| opendevreview | David Wilde proposed openstack/releases master: Create new keystone-tempest-plugin release for 2023.1 https://review.opendev.org/c/openstack/releases/+/915747 | 16:37 |
| opendevreview | sean mooney proposed openstack/releases master: release whitebox-tempest-plugin https://review.opendev.org/c/openstack/releases/+/915751 | 17:00 |
| opendevreview | sean mooney proposed openstack/releases master: release whitebox-tempest-plugin https://review.opendev.org/c/openstack/releases/+/915751 | 18:45 |
| opendevreview | sean mooney proposed openstack/releases master: release whitebox-tempest-plugin https://review.opendev.org/c/openstack/releases/+/915751 | 18:53 |
| opendevreview | sean mooney proposed openstack/releases master: release whitebox-tempest-plugin https://review.opendev.org/c/openstack/releases/+/915751 | 18:56 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!