| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-03-07 | |||
| 16:19:13 | bauzas | #link https://releases.openstack.org/antelope/schedule.html | |
| 16:19:19 | bauzas | #info Antelope-rc1 was this Monday | |
| 16:19:40 | bauzas | so, we're now in a duplicity period, where we are both on Bobcat and Antelope timeframes :) | |
| 16:20:01 | bauzas | if you've seen Tenet, you got it | |
| 16:20:08 | bauzas | (the movie) | |
| 16:20:19 | bauzas | now, we have a 2023.1 branch | |
| 16:20:43 | elodilles | ~o~ | |
| 16:20:53 | bauzas | #info as a reminder, no backports are possible on the 2023.1 branch *unless* they are regression bugfixes | |
| 16:21:27 | bauzas | and accordingly all stable branches go on a quiet period since they're now dependent on the antelope branch | |
| 16:22:23 | bauzas | #link https://etherpad.opendev.org/p/nova-antelope-rc-potential | |
| 16:22:46 | bauzas | fwiw, our release notes are currently broken to be shown | |
| 16:22:51 | bauzas | for Antelope | |
| 16:23:19 | sean-k-mooney | we can still merge exsting backport but noting to 2023.1 | |
| 16:23:22 | bauzas | context : https://review.opendev.org/c/openstack/nova/+/876553 | |
| 16:23:24 | sean-k-mooney | that is not for an rc | |
| 16:23:56 | bauzas | sean-k-mooney: well, if the original patch is on Antelope, sure | |
| 16:24:35 | sean-k-mooney | we have plent of open backport on exsting stable branch that coudl use review | |
| 16:24:36 | bauzas | elodilles: iiuc, we'll need to enable the new reno ordering in our releasenotes ? | |
| 16:24:49 | bauzas | once the reno patch got landed | |
| 16:24:50 | elodilles | bauzas: fyi, reno workaround has landed, but not yet released | |
| 16:24:59 | bauzas | oh, missed that | |
| 16:25:08 | elodilles | bauzas: and we don't need to do anything, but use the new reno release | |
| 16:25:10 | bauzas | sean-k-mooney: yup, don't disagree | |
| 16:25:11 | sean-k-mooney | do we need to do any changes once its released | |
| 16:25:22 | sean-k-mooney | or will the release notes get rebuilt automatically | |
| 16:25:27 | bauzas | elodilles: ah, right, so dhellmann's proposition was accepted | |
| 16:25:36 | sean-k-mooney | ok cool | |
| 16:25:43 | sean-k-mooney | if we dont need to do anything great | |
| 16:25:54 | bauzas | sean-k-mooney: yeah, so there was a patch up for opting-in to the new reno ordering | |
| 16:26:05 | sean-k-mooney | by use the new reno does that mean increase the min version in requirements | |
| 16:26:09 | bauzas | but doug said he was ok with having it by default | |
| 16:26:24 | sean-k-mooney | or just realy on upper-constratis | |
| 16:26:28 | bauzas | sean-k-mooney: reno isn't part of our requirements | |
| 16:26:36 | bauzas | (unless I'm wrong) | |
| 16:26:38 | sean-k-mooney | its in our doc requirements i think | |
| 16:26:47 | bauzas | that's a specific target, which isn't docs | |
| 16:26:54 | elodilles | actually, it is part of upper-constraints | |
| 16:26:59 | sean-k-mooney | https://github.com/openstack/nova/blob/master/doc/requirements.txt#L13 | |
| 16:27:06 | bauzas | https://github.com/openstack/nova/blob/master/tox.ini#L238 | |
| 16:27:15 | elodilles | but for master branch (bobcat) I think it will be soon possible to bump | |
| 16:27:36 | sean-k-mooney | https://github.com/openstack/nova/blob/master/tox.ini#L238-L242 | |
| 16:27:43 | sean-k-mooney | the release notes use the docs requirements file | |
| 16:27:47 | bauzas | sean-k-mooney: snap | |
| 16:28:01 | sean-k-mooney | so ya it will automatically get picked up from uc | |
| 16:28:12 | sean-k-mooney | but im wonderign if we want to block the older releases or not | |
| 16:28:19 | sean-k-mooney | we dont have too but we could | |
| 16:28:30 | bauzas | it's backwards-compatible | |
| 16:28:44 | bauzas | so I don't think we need | |
| 16:28:57 | sean-k-mooney | yep i was more thinking of a signal to packages | |
| 16:29:06 | sean-k-mooney | but im fine with not bumping the min version | |
| 16:29:19 | bauzas | elodilles: the new reno release is a x. version ? | |
| 16:29:25 | bauzas | or a .y ? | |
| 16:29:35 | sean-k-mooney | all of the offical release notes will be update proeprly | |
| 16:29:41 | elodilles | it will be a MAJOR version bump | |
| 16:29:46 | bauzas | cool, so x. | |
| 16:29:57 | elodilles | yepp | |
| 16:30:04 | bauzas | sean-k-mooney: well technically, our master branch will need this | |
| 16:30:22 | sean-k-mooney | yep we would merge it in master and backprot to 2023.1 | |
| 16:30:25 | bauzas | maybe the 2023.1 branch will need it too | |
| 16:30:37 | sean-k-mooney | reno>=4.0.0 | |
| 16:30:48 | bauzas | but for other branches, they shouldn't mention the antelope notes | |
| 16:30:54 | sean-k-mooney | correct | |
| 16:31:07 | sean-k-mooney | we cant bump the requirement on older banches anyway | |
| 16:31:20 | bauzas | sean-k-mooney: the patch in question is https://review.opendev.org/c/openstack/nova/+/876553 | |
| 16:31:22 | sean-k-mooney | we only have the opertunity to do it on 2023.1 because we have not releassed yet | |
| 16:31:47 | bauzas | yes | |
| 16:31:52 | bauzas | and we'll need it once we tag | |
| 16:32:15 | bauzas | a stable antelope release, I mean | |
| 16:32:27 | bauzas | oh wait no | |
| 16:32:34 | bauzas | maybe it's unnecessaru | |
| 16:32:46 | bauzas | our gits tags will mention the project tags, not the openstack release | |
| 16:32:59 | bauzas | the problem with reno is about the branches ordering | |
| 16:33:14 | bauzas | anyway, we'll figure that out | |
| 16:33:20 | bauzas | no need to spec it up too | |
| 16:33:23 | bauzas | here | |
| 16:33:49 | bauzas | we also need to merge https://review.opendev.org/c/openstack/nova/+/875621/ but I need to respin it | |
| 16:34:13 | sean-k-mooney | reno also supprots metadata in the commit log to denote a release | |
| 16:34:20 | sean-k-mooney | so that might also help | |
| 16:34:27 | sean-k-mooney | but ya we can proably move on | |
| 16:34:32 | sean-k-mooney | we willl figure this out | |
| 16:34:40 | bauzas | last but not the least (rc1 is a busy time for a PTL), I did a bit of launchpad scrubbing | |
| 16:35:05 | bauzas | #info https://blueprints.launchpad.net/nova/antelope now shows 'deferred' for approved but non-implemented Blueprints | |
| 16:35:33 | bauzas | the 2023.2 specs directory is open and I already fast-approved two specs that were accepted in Antelope | |
| 16:36:04 | bauzas | I'll add the launchpad bobcat series after the meeting so technically, we can now start to approve new specs and specless blueprints | |
| 16:36:20 | sean-k-mooney | ack | |
| 16:36:35 | sean-k-mooney | we should start using the placement repo for placement thigns now too | |
| 16:36:38 | bauzas | that's it for this topic (larger than usual) | |
| 16:36:45 | sean-k-mooney | were started to do that partly last cycle but not consitently | |
| 16:36:58 | bauzas | sean-k-mooney: placement will also have its own launchpad bobcat series | |
| 16:37:05 | sean-k-mooney | yes | |
| 16:37:16 | bauzas | and yeah, we have to mimic the same than nova | |
| 16:37:25 | bauzas | as we agreed on stopping to use Storyboard | |
| 16:37:27 | sean-k-mooney | but we used a mix of stories and task instory board and some lanchpad stuff | |
| 16:37:39 | sean-k-mooney | so lets try and just use lanuchpad this time | |
| 16:37:58 | bauzas | that's a good point, I should somehow signal in Storyboard that we no longer support it for Placezment | |
| 16:38:23 | sean-k-mooney | ideally we should see if we can make it readonly and/or clsoe the exiting issues | |
| 16:38:38 | bauzas | #action bauzas to clean-up the stories in Storyboard and tell their owners to recreate a Launchpad bug or blueprint if they wish to carry it on | |
| 16:39:05 | bauzas | moving on | |
| 16:39:17 | bauzas | #info Uggla and auniyal are the new release liaisons https://review.opendev.org/c/openstack/releases/+/876758 | |
| 16:39:29 | elodilles | \o/ | |