| *** ysandeep|out is now known as ysandeep | 05:27 | |
| *** ysandeep is now known as ysandeep|lunch | 07:26 | |
| *** amoralej|off is now known as amoralej | 08:15 | |
| *** ysandeep|lunch is now known as ysandeep | 08:41 | |
| noonedeadpunk | Hey! 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 |
|---|---|---|
| noonedeadpunk | As eventually we kind of ready to make stable release from rc1. BUT, it's a branching stage, so does not include .gitreview and tox updated | 08:43 |
| noonedeadpunk | make rc2 with these 2 simple changes is... well.. | 08:44 |
| hberaud | noonedeadpunk: what do you mean by "stable tags should be based on RCs" do you mean that stable branches should cut from RCs? | 09:22 |
| noonedeadpunk | nope, 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 rc2 | 09:23 |
| noonedeadpunk | which leads me to question if it always must be RC as a base for X.0.0 tag | 09:25 |
| noonedeadpunk | as 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 |
| hberaud | yes AFAIK I'd argue that a stable tag should be based on an RC | 09:26 |
| hberaud | I see | 09:26 |
| noonedeadpunk | just I have some vague memories that check could fail othervise, but I'm not really sure about that) | 09:26 |
| noonedeadpunk | so decided to ask for opinion | 09:27 |
| noonedeadpunk | as eventually it's kind of useless RC if it must be that way... | 09:27 |
| *** ysandeep is now known as ysandeep|afk | 09:35 | |
| hberaud | noonedeadpunk: I don't think we need producing an RC only for these 2 changes (.gitreview). Let's us the RC1 for your stable tag | 09:43 |
| hberaud | s/us/use | 09:43 |
| noonedeadpunk | ok, let me try then:) | 09:52 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Xena https://review.opendev.org/c/openstack/releases/+/821683 | 09:53 |
| *** ysandeep|afk is now known as ysandeep | 10:32 | |
| elodilles | noonedeadpunk: i've commented on the patch: i think what hberaud meant is that you don't need an rc2, you can simply release rc1 instead | 11:46 |
| elodilles | hberaud: correct me if i'm wrong :) | 11:46 |
| noonedeadpunk | ah, I guess you're right | 11:48 |
| noonedeadpunk | I read what I wanted to read:) | 11:49 |
| elodilles | :) | 12:10 |
| *** ysandeep is now known as ysandeep|brb | 12:21 | |
| *** ysandeep|brb is now known as ysandeep | 12:48 | |
| hberaud | elodilles: yes you are right | 13:06 |
| *** amoralej is now known as amoralej|lunch | 13:16 | |
| elodilles | ack, thx | 13:47 |
| *** amoralej|lunch is now known as amoralej | 14:04 | |
| *** ysandeep is now known as ysandeep|out | 14:13 | |
| noonedeadpunk | oh, btw, shouldn't EOLing repos remove branch? | 15:05 |
| noonedeadpunk | https://opendev.org/openstack/openstack-ansible-os_glance as example for Ocata | 15:06 |
| elodilles | noonedeadpunk: nope, but I'll run the script to remove it then o:) | 15:08 |
| noonedeadpunk | aha, gotcha | 15:09 |
| noonedeadpunk | we most likely will eol more very soon :) | 15:19 |
| elodilles | sorry to hear that :( but if it's not maintained, then of course, it's understandable :) | 15:42 |
| noonedeadpunk | well, I'm not sure how P is relevant nowadays anyway | 16:02 |
| noonedeadpunk | but will reduce amount of branches at least... | 16:03 |
| noonedeadpunk | we're still far behind Octavia in EOLing things hehe | 16:03 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Xena https://review.opendev.org/c/openstack/releases/+/821584 | 16:39 |
| *** marios is now known as marios|out | 16:46 | |
| *** beekneemech is now known as bnemec | 17:08 | |
| opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: [OpenStackAnsible Roles] Transition Pike to End of Life https://review.opendev.org/c/openstack/releases/+/821742 | 17:20 |
| *** amoralej is now known as amoralej|off | 17:26 | |
| elodilles | noonedeadpunk: fyi, this needs to be abandoned: https://review.opendev.org/c/openstack/openstack-ansible/+/795690 | 18:40 |
| elodilles | noonedeadpunk: firstly, because the branch is already eol'd and no patches should merge | 18:40 |
| elodilles | noonedeadpunk: on the other hand, branches cannot be deleted if there are open patches in gerrit against them | 18:41 |
| elodilles | noonedeadpunk: 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 that | 18:57 |
| elodilles | noonedeadpunk: so in short: part of OpenStack Ansible's EOL'd ocata branches will be deleted some days later this week if everything goes well | 18:59 |
| elodilles | it shouldn't be a problem, i only ask you to please do not open/approve/merge any patches on those old ocata branches | 19:00 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!