Tuesday, 2022-05-24

opendevreviewGhanshyam proposed openstack/releases master: [Tempest] Tag ussuri-last  https://review.opendev.org/c/openstack/releases/+/84303900:58
opendevreviewTakashi Kajinami proposed openstack/releases master: Puppet OpenStack: Change release model to cycle-with-rc  https://review.opendev.org/c/openstack/releases/+/84309802:39
*** dviroel|out is now known as dviroel11:21
opendevreviewMerged openstack/releases master: Puppet OpenStack: Change release model to cycle-with-rc  https://review.opendev.org/c/openstack/releases/+/84309812:53
opendevreviewCorey Bryant proposed openstack/releases master: New stable releases for Neutron  https://review.opendev.org/c/openstack/releases/+/84297113:32
tkajinamelodilles, hi. it'd be nice if I can hear your thoughts on https://review.opendev.org/c/openstack/releases/+/841831 .14:00
tkajinamthis would be related to the problem with old newton releases you earlier raised in ml14:00
elodillestkajinam: yepp, i've started the cleanup, this patch will need manual tagging (as our jobs will skip the tagging part because the branch is EOL'd already), so i wanted to merge it when i get there o:)14:13
tkajinamelodilles, thanks. do you want me to WIP the patch or do you mind posting -1 to keep it open ?14:14
tkajinam-1 from you might be helpful because you can unblock it when you want14:15
elodillestkajinam: sure, i'll mark it with -1 for now14:16
tkajinamelodilles, thanks !14:16
elodillesnp :)14:22
*** whoami-rajat__ is now known as whoami-rajat15:50
*** dviroel is now known as dviroel|lunch15:58
*** marios is now known as marios|out15:58
opendevreviewMohammed Naser proposed openstack/releases master: Create EOL tags for neutron-vpnaas  https://review.opendev.org/c/openstack/releases/+/84316715:59
gmannttx: elodilles release name/number discussion meeting started https://meet.google.com/gwi-cphb-rya16:00
ttxI'm on16:01
ttxelodilles: looks like we'll end up with stable/2023.1 and aardvark-1 milestones16:30
ttxthat way we avoid technical constraints on the names16:31
elodillesttx: ack, thanks for the info!16:32
ttxstill udner discussion but that's the leading option16:32
elodillesttx: ack16:33
ttxOK so basically the stable branch has to be named after the version number, but the reelase team can name their cycle milestones however they want16:40
elodillesttx: sounds OK16:40
elodilleswe kind of expected this result16:47
*** dviroel|lunch is now known as dviroel16:58
clarkbI missed the meeting but won't that cause extra confusion if we have a branch called stable/2023.1 and tag 18.0.0 on that branch?17:22
elodillesclarkb: good question. hopefully not. i mean, hopefully people get used to it. release management team would prefer to keep the names where it is possible, but that was decided, so we will live with it17:49
opendevreviewCorey Bryant proposed openstack/releases master: New stable releases for Neutron  https://review.opendev.org/c/openstack/releases/+/84297119:42
*** dviroel is now known as dviroel|out21:11
gmannelodilles: when stable/victoria is going to be EM?22:19
gmannbecause that will help me to drop py3.6|7 support from tempest master otherwise grenade jobs on stable/victoria will fail22:21
gmannor may not be, if ussuri will use old tempest then it should be ok. I think need to go one by one on these22:23
gmannelodilles: ah it is done, sorry I did not realize it https://review.opendev.org/c/openstack/releases/+/83799523:04
gmannthanks 23:04

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