15:00:41 <carloss> #startmeeting manila
15:00:41 <opendevmeet> Meeting started Thu Nov 30 15:00:41 2023 UTC and is due to finish in 60 minutes.  The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:41 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:41 <opendevmeet> The meeting name has been set to 'manila'
15:00:46 <carthaca> hi
15:00:52 <jayaanand> hi
15:00:53 <gireesh> hi
15:01:02 <vhari> hi
15:01:02 <carloss> courtesy ping: vkmc dviroelvhari gouthamr msaravan pulluri
15:01:19 <carloss> s/dviroelvhari/dviroel
15:01:31 <msaravan> hi
15:02:28 <gouthamr> hello o/
15:02:32 <haixin> o/
15:02:54 <ashrodri> o/
15:03:20 <dviroel> o/
15:04:37 <carloss> o/ hello everyone and welcome!
15:05:00 <carloss> hope everyone that had the last week's break had time to recharge the batteries and have a good time :D
15:05:15 <carloss> today's meeting agenda:
15:05:17 <carloss> #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting
15:07:03 <carloss> first topic:
15:07:05 <carloss> #topic Announcements
15:07:21 <carloss> Schedule and deadlines
15:07:23 <carloss> #link https://releases.openstack.org/caracal/schedule.html
15:09:44 <carloss> so we're just past m1
15:11:06 <carloss> and we have been working on the specs and reviews
15:11:16 <carloss> and getting started with the development of some features
15:12:29 <carloss> i am planning to do some launchpad cleanup today/tomorrow
15:12:53 <carloss> but I think our focus now should mostly be on the specs and the bugs and features we are planning to implement during this cycle
15:14:43 <carloss> and I have finally proposed the manila-specific deadlines to the schedule:
15:14:44 <carloss> #link https://review.opendev.org/c/openstack/releases/+/902305
15:15:10 <carloss> I had this change ready in the beginning of the week but forgot to send it to gerrit
15:15:59 <carloss> some dates we don't have yet are: our traditional hackathon and bugsquash for this cycle
15:16:13 <carloss> the bugsquash I was thinking of doing it towards the end of the release
15:17:36 <carloss> do you have any thoughts on this?
15:18:08 <ashrodri> do we have a "theme" for the hackathon?
15:19:07 <carloss> I don't think so yet... we could focus on tech debt but that would make it three in a row, so maybe we could try something different
15:19:20 <vhari> based on bug stats, it's a good time for another review based bugsquash
15:19:59 <vhari> the bugsquash could be a combination of these themes
15:20:28 <carloss> ah, true vhari  - maybe we can do the bugsquash earlier in the cycle?
15:20:36 <carloss> so bugs will be shipping within this release
15:20:50 <carloss> as in the previous one, most bugs ended up slipping to the next release
15:21:16 <vhari> that would be a good idea, there are 32 in-progress bugs
15:22:13 <vhari> 30% of which targeted  caracal-1
15:23:32 <carloss> awesome! maybe right after m-2 is a good idea?
15:23:45 <carloss> ~Jan 15
15:23:48 <carloss> wdyt?
15:23:51 <vhari> +1
15:24:33 <carloss> ack, I'll add that to the releases patch I just sent
15:25:09 <vhari> awesome ty carloss :)
15:25:22 <carloss> alright, one more thing for announcements:
15:25:50 <carloss> np, ty vhari :D
15:26:22 <carloss> I'd like to cancel the next week's meeting, as I'll be unable to attend, and we'll have some people from the audience on PTO
15:26:52 <carloss> it feels like we've been cancelling a lot of meetings lately, but I think we're just unlucky with this year's calendar
15:26:58 * gouthamr late, but acks the jan 15th bugsquash idea
15:27:46 <vhari> carlos  also a late cycle mini-bugsquash (time permitting) themed "stale bugs"  would help reduce the backlog
15:28:47 <carloss> vhari++ yeah, we can do that too
15:29:27 <vhari> mini-bugsquash would include less bugs, and hence  requires less  capacity
15:30:20 <carloss> ++, maybe rc1 week or the week after?
15:30:27 <carloss> as I assume most of the development will be done
15:30:47 <vhari> that would be awesome carloss++
15:31:27 <carloss> ack, I'll propose the changes
15:31:53 <carloss> that's all I had for announcements. Do you have an announcement to share with us today?
15:33:21 <carloss> taking silence as no
15:33:29 <carloss> #topic Review Focus: backports
15:33:35 <carloss> before we focus on the backports:
15:34:29 <carloss> I'l like to request some reviews to the ongoing specs:
15:34:38 <carloss> #link https://review.opendev.org/c/openstack/manila-specs/+/898999 Add spec for share encryption
15:34:39 <carloss> and
15:35:06 <carloss> #link https://review.opendev.org/c/openstack/manila-specs/+/901700 Add spec for share/share-snapshot deferred deletion
15:35:59 <carloss> ashrodri msaravan jayaanand haixin gireesh: can I have your eyes on the specs? :D
15:36:16 <jayaanand> ok
15:37:02 <carloss> awesome! thank you very much
15:37:07 <carloss> sorry I hijacked some time
15:37:18 <carloss> gouthamr: would you like to get started with $topic? :)
15:37:36 <gouthamr> sure thing carloss
15:38:06 <gouthamr> lets start with the fact that we're transitioning several open branches to EOL, and several to "unmaintained" status as we shared last meeting
15:38:34 <gouthamr> #link https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html (TC resolution - 2023-07-24 Unmaintained status replaces Extended Maintenance)
15:39:13 <gouthamr> we've always strived to backport things with adequate testing.. but, these backports have been languishing for a while without attention..
15:40:09 <gouthamr> thanks carloss haixin dviroel for taking a look .. i wanted to see if we can do a small review jam and get the remaining ones moving
15:41:29 <gouthamr> 2023.2 and 2023.1 seem better, and we'll _maintain_ these for a little bit
15:41:33 <gouthamr> #link https://review.opendev.org/q/project:openstack/manila+status:open+branch:stable/zed (Zed)
15:41:40 <gouthamr> #link https://review.opendev.org/q/project:openstack/manila+status:open+branch:stable/yoga (Yoga)
15:41:44 <gouthamr> #link https://review.opendev.org/q/project:openstack/manila+status:open+branch:stable/yoga (Xena)
15:41:55 <gouthamr> #link https://review.opendev.org/q/project:openstack/manila+status:open+branch:stable/wallaby (Wallaby)
15:42:20 <carloss> > i wanted to see if we can do a small review jam and get the remaining ones moving
15:42:20 <carloss> absolutely! and thanks for bringing this up gouthamr
15:43:17 <gouthamr> it'd be a great deal of help if we can clean these remaining ones out..
15:43:23 <msaravan> I'll abandon my patch https://review.opendev.org/c/openstack/manila/+/892402 as it is not valid for Wallaby;
15:44:09 <gouthamr> cool stuff msaravan
15:45:17 <msaravan> Thank you for catching it goutham. Thorough review you did,  and it reduced the impact on wallaby.
15:45:53 <gouthamr> you're welcome..
15:46:47 <gouthamr> i think it'd make the job a whole lot easier for carloss dviroel haixin and myself if there were more eyes on the other changes :) i think if CI has been passing, and there's no -1s, we can go ahead and merge many of these
15:47:06 <gouthamr> the +1s ofcourse will give us confidence
15:48:46 <carloss> ++
15:50:24 <carloss> so do you feel we should work on review assignments or do things more proactively?
15:52:21 <gouthamr> i think we can do assignments with the cores
15:52:51 <gouthamr> the rest can be opportunistic/proactive i think..
15:52:57 <carloss> ack
15:53:19 <carloss> +1
15:54:04 <gouthamr> vendor driver changes in particular will need +1s, or they may not be appropriate to merge i think
15:54:42 <gouthamr> i.e., i wouldn't have the confidence that something works well, especially because we have poor CI coverage for these stable branches
15:54:48 <carloss> yeah, I agree
15:55:15 <carloss> and I think almost half of the changes are touching 3rd party drivers
15:57:28 <gouthamr> +1
15:58:07 <gouthamr> that's all i had, thank you carloss
15:58:26 <carloss> so we can assign some third party reviewers and you can assign other people to the changes
15:58:42 <carloss> and we can work with the stable branch cores to merge the remaining changes in the next couple of weeks
15:58:47 <carloss> thank you for bringing this up, gouthamr
15:59:00 <gouthamr> ++
15:59:02 <carloss> I believe that's all I had for $topic too
15:59:13 <carloss> we're at the top of the hour
15:59:35 <carloss> sorry for not having time for bug triaging vhari - we can get back to the stale bug in two weeks time
15:59:44 <carloss> but if there's something pressing, please let us know
15:59:54 <carloss> how does that sound? :)
15:59:57 <vhari> np carloss .. there were no new bugs to triage this week :)
16:00:04 <carloss> ack vhari, ty :D
16:00:14 <carloss> thank you for joining folks!
16:00:19 <carloss> see you on #openstack-manila
16:00:22 <carloss> #endmeeting