| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-03-07 | |||
| 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/ | |
| 16:39:53 | bauzas | elodilles: don't feel overlooked :p | |
| 16:39:58 | elodilles | :] | |
| 16:40:05 | elodilles | i won't :) | |
| 16:40:09 | auniyal | we need to update the bug tracker link here https://opendev.org/openstack/placement | |
| 16:40:39 | bauzas | auniyal: excellent point, fancy creating a change against it ? | |
| 16:40:45 | auniyal | yes | |
| 16:40:52 | sean-k-mooney | i belvie that is in the governance repo | |
| 16:40:53 | bauzas | cool, thanks | |
| 16:41:02 | sean-k-mooney | posibly the main config repo | |
| 16:41:07 | bauzas | sean-k-mooney: I'm pretty it isn't | |
| 16:41:13 | bauzas | sure* | |
| 16:41:38 | bauzas | I've recently seen the project yaml files and I don't remember any mention of the bug tracking system | |
| 16:41:52 | bauzas | but I could have missed it | |
| 16:42:00 | bauzas | anyway, action is on me | |
| 16:42:22 | bauzas | next topic, and I'd like to see some quorum on it | |
| 16:42:24 | bauzas | #topic vPTG Planning | |
| 16:42:34 | bauzas | the usual reminder : | |
| 16:42:36 | bauzas | #link https://www.eventbrite.com/e/project-teams-gathering-march-2023-tickets-483971570997 Register your free ticket | |
| 16:43:02 | bauzas | even if this is a free event, it helps the foundation folks to correctly identify the attendance | |
| 16:43:21 | bauzas | #link https://etherpad.opendev.org/p/nova-bobcat-ptg Draft PTG etherpad | |
| 16:43:29 | bauzas | #info we need to agree on the agenda and how many slots we book | |
| 16:43:44 | bauzas | the ptg website is up | |
| 16:44:04 | bauzas | #link https://ptg.opendev.org/ptg.html | |
| 16:44:34 | bauzas | as you see, I've booked four hour slots per day between Tues and Friday | |
| 16:44:50 | bauzas | this is quite a large time, but I don't want to consume all of them | |
| 16:45:20 | bauzas | anyone having other opinions on the strawman proposal of 4x 4 hours ? | |
| 16:45:46 | bauzas | this would be 13:00-17:00 UTC | |
| 16:46:22 | bauzas | ideally, I'd also want to attend the TC sessions so I may require some co-chair if it conflicts | |
| 16:47:11 | bauzas | again, anyone having concerns with this proposal ? | |
| 16:47:57 | sean-k-mooney | no concerns really i assume we will subdevide the 4 hour into 4 50min slots and 10 min breaks | |
| 16:48:09 | bauzas | that's heard and agreed | |
| 16:48:21 | bauzas | I'm not a fan of long running days | |
| 16:48:26 | bauzas | this is exhausting at most. | |