16:00:16 <priteau_> #startmeeting blazar
16:00:16 <opendevmeet> Meeting started Thu Feb 10 16:00:16 2022 UTC and is due to finish in 60 minutes.  The chair is priteau_. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:16 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:16 <opendevmeet> The meeting name has been set to 'blazar'
16:00:21 <priteau_> #topic Roll call
16:00:57 <priteau_> o/
16:01:08 <mppowers> o/
16:01:25 <priteau_> How are you doing mppowers?
16:01:40 <mppowers> I am good, how are you?
16:01:57 <priteau_> Doing well, thanks.
16:02:11 <priteau_> Should we expect Jason?
16:02:41 <mppowers> Yes, I'll ping
16:03:00 <mppowers> Actually he isn't online yet
16:05:33 <priteau_> Maybe let's start with discussing your current patches
16:05:38 <priteau_> #topic Yoga release
16:05:58 <priteau_> We're getting closer to the end of the release cycle
16:06:13 <priteau_> Final release for non-client libraries next week: blazar-nova
16:06:26 <priteau_> Feature freeze in two weeks
16:07:59 <priteau_> I am afraid some recent changes have made this a merge conflict: https://review.opendev.org/c/openstack/blazar/+/820607
16:08:37 <mppowers> That is alright, with such a big change it is inevitable
16:10:02 <priteau_> Anyway we need to merge the two underlying patches first
16:10:07 <priteau_> 810298: Add resource properties discovery API | https://review.opendev.org/c/openstack/blazar/+/810298
16:10:10 <priteau_> 820255: Remove RPC layer from API | https://review.opendev.org/c/openstack/blazar/+/820255
16:10:16 <priteau_> They're both ready to go?
16:10:23 <mppowers> Yes, both are ready
16:10:41 <diurnalist> hello, sorry i'm late
16:11:10 <priteau_> Hi diurnalist
16:11:14 <priteau_> No problem
16:11:46 <priteau> We were discussing Mark's patches
16:12:06 <priteau> https://review.opendev.org/c/openstack/blazar/+/810298 and https://review.opendev.org/c/openstack/blazar/+/820255 are both ready for review again
16:12:45 <priteau> I'll aim to review them tomorrow
16:13:44 <priteau> I've moved them at the top of the review list
16:13:45 <priteau> #link https://etherpad.opendev.org/p/blazar-whiteboard
16:13:56 <mppowers> Great! Thanks
16:16:01 <priteau> What do we want to prioritise for Yoga?
16:17:18 <priteau> We could potentially get everything in the Priorities for main feature freeze merged?
16:17:25 <priteau> We have two weeks left
16:18:00 <diurnalist> yes, i think so...
16:19:12 <priteau> I am still working on my additional preemptible patches, having more issues with unit tests than the actual code unfortunately :/
16:20:56 <diurnalist> i'm reviewing some of your other things now
16:21:41 <priteau> Just noticed there is an unresolved comment here, can it be marked done? https://review.opendev.org/c/openstack/blazar/+/810298/3..11/blazar/plugins/base.py#b111
16:22:26 <mppowers> Yes, that is fixed now. I'll mark them as resolved
16:22:38 <priteau> Just noticed a small issue in the process
16:23:41 <mppowers> sounds good, I should be able to quickly fix it soon
16:25:08 <priteau> I've not done a full review, hopefully there won't be more changes
16:26:10 <opendevreview> Merged openstack/blazar-dashboard master: Updating python testing classifier as per Yoga testing runtime  https://review.opendev.org/c/openstack/blazar-dashboard/+/826982
16:26:48 <mppowers> Yes, it should be alright. the resource property API was already reviewed once, and so I do not anticipate many more needed changes
16:29:22 <priteau> If it requires changes that could be fixed with a follow-up patch, I will prefer that approach so we can merge faster
16:30:42 <priteau> https://review.opendev.org/c/openstack/blazar/+/761994 is in merge conflict, may be trivial to fix
16:31:57 <priteau> I will also cherry pick some patches to stable branches, so we will see how well CI works
16:32:15 <diurnalist> i'll look about the merge conflict
16:32:24 <priteau> thanks
16:32:48 <priteau> I think that's all about active patches
16:33:13 <priteau> The next topic I wanted to discuss was...
16:33:19 <priteau> #topic PTL candidacy
16:33:28 <priteau> It's already this time of the year
16:33:56 <priteau> Nominations are open until Feb 15, 2022 23:45 UTC.
16:34:35 <priteau> In a more active project I would probably say it's time for someone else to carry the torch
16:34:59 <priteau> So unless diurnalist you are interested in being PTL, I am happy to continue for the Z cycle
16:37:10 <priteau> In any case I don't think we want the project to be without leadership
16:37:43 <diurnalist> i'm happy for you to be PTL - is there a PTL handbook or something btw? it seems there are lots of process-y things that i pick up ad-hoc
16:38:15 <priteau> #link https://docs.openstack.org/project-team-guide/ptl.html
16:38:32 <diurnalist> aha :)
16:39:06 <priteau> It's mostly synchronising with the openinfra foundation (for PTG and summit) and release management
16:41:26 <priteau> I'll put in my candidacy early next week in this case
16:41:34 <priteau> While you keep learning ;-)
16:41:48 <priteau> #topic AOB
16:42:22 <priteau> Anything else you would like to discuss today?
16:42:34 <priteau> There was the PTG meeting, I think diurnalist you said you would not be available
16:42:48 <diurnalist> correct, i will be on vacation
16:42:49 <priteau> So we would schedule something the week before or after
16:43:09 <priteau> or two weeks before / after, whenever it works for you
16:43:15 <diurnalist> ok
16:43:27 <priteau> I'll still hold a meeting in case someone wants to discuss
16:43:48 <priteau> Any else for today?
16:43:55 <mppowers> nothing else from me
16:45:59 <priteau> Thanks, let's wrap up then!
16:46:05 <priteau> Thanks for joining
16:46:08 <priteau> #endmeeting
16:48:44 <priteau_> #endmeeting