Tuesday, 2021-12-14

*** ysandeep|out is now known as ysandeep05:27
*** ysandeep is now known as ysandeep|lunch07:26
*** amoralej|off is now known as amoralej08:15
*** ysandeep|lunch is now known as ysandeep08:41
noonedeadpunkHey! Have a question about releasing. Am I right that all stable tags should be based on RCs? As I'm not sure what to do best with that...08:43
noonedeadpunkAs eventually we kind of ready to make stable release from rc1. BUT, it's a branching stage, so does not include .gitreview and tox updated08:43
noonedeadpunkmake rc2 with these 2 simple changes is... well.. 08:44
hberaudnoonedeadpunk: what do you mean by "stable tags should be based on RCs" do you mean that stable branches should cut from RCs?09:22
noonedeadpunknope, not that. From what I see as examples from previous releases https://opendev.org/openstack/releases/src/branch/master/deliverables/wallaby/openstack-ansible.yaml#L32 is SHA of rc209:23
noonedeadpunkwhich leads me to question if it always must be RC as a base for X.0.0 tag09:25
noonedeadpunkas we're not going to have any functional changes from rc1, except merging .gitreview after branching (as we're late with that anyway)09:26
hberaudyes AFAIK I'd argue that a stable tag should be based on an RC09:26
hberaudI see09:26
noonedeadpunkjust I have some vague memories that check could fail othervise, but I'm not really sure about that)09:26
noonedeadpunkso decided to ask for opinion09:27
noonedeadpunkas eventually it's kind of useless RC if it must be that way...09:27
*** ysandeep is now known as ysandeep|afk09:35
hberaudnoonedeadpunk: I don't think we need producing an RC only for these 2 changes (.gitreview). Let's us the RC1 for your stable tag09:43
noonedeadpunkok, let me try then:)09:52
opendevreviewDmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Xena  https://review.opendev.org/c/openstack/releases/+/82168309:53
*** ysandeep|afk is now known as ysandeep10:32
elodillesnoonedeadpunk: i've commented on the patch: i think what hberaud meant is that you don't need an rc2, you can simply release rc1 instead11:46
elodilleshberaud: correct me if i'm wrong :)11:46
noonedeadpunkah, I guess you're right11:48
noonedeadpunkI read what I wanted to read:)11:49
*** ysandeep is now known as ysandeep|brb12:21
*** ysandeep|brb is now known as ysandeep12:48
hberaudelodilles: yes you are right13:06
*** amoralej is now known as amoralej|lunch13:16
elodillesack, thx13:47
*** amoralej|lunch is now known as amoralej14:04
*** ysandeep is now known as ysandeep|out14:13
noonedeadpunkoh, btw, shouldn't EOLing repos remove branch?15:05
noonedeadpunkhttps://opendev.org/openstack/openstack-ansible-os_glance as example for Ocata15:06
elodillesnoonedeadpunk: nope, but I'll run the script to remove it then o:)15:08
noonedeadpunkaha, gotcha15:09
noonedeadpunkwe most likely will eol more very soon :)15:19
elodillessorry to hear that :( but if it's not maintained, then of course, it's understandable :)15:42
noonedeadpunkwell, I'm not sure how P is relevant nowadays anyway16:02
noonedeadpunkbut will reduce amount of branches at least...16:03
noonedeadpunkwe're still far behind Octavia in EOLing things hehe16:03
opendevreviewDmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Xena  https://review.opendev.org/c/openstack/releases/+/82158416:39
*** marios is now known as marios|out16:46
*** beekneemech is now known as bnemec17:08
opendevreviewDmitriy Rabotyagov proposed openstack/releases master: [OpenStackAnsible Roles] Transition Pike to End of Life  https://review.opendev.org/c/openstack/releases/+/82174217:20
*** amoralej is now known as amoralej|off17:26
elodillesnoonedeadpunk: fyi, this needs to be abandoned: https://review.opendev.org/c/openstack/openstack-ansible/+/79569018:40
elodillesnoonedeadpunk: firstly, because the branch is already eol'd and no patches should merge18:40
elodillesnoonedeadpunk: on the other hand, branches cannot be deleted if there are open patches in gerrit against them18:41
elodillesnoonedeadpunk: and a heads-up: i've started to run the branch cleanup script (that deletes the eol'd branches) and with it it seems that a zuul bug can be successfully reproduced :) infra team is planning to implement a fix for that and i offered to delay the branch cleanup to be able to test the fix with that18:57
elodillesnoonedeadpunk: so in short: part of OpenStack Ansible's EOL'd ocata branches will be deleted some days later this week if everything goes well18:59
elodillesit shouldn't be a problem, i only ask you to please do not open/approve/merge any patches on those old ocata branches19:00

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!