14:00:34 <elodilles> #startmeeting releaseteam 14:00:34 <opendevmeet> Meeting started Fri Nov 5 14:00:34 2021 UTC and is due to finish in 60 minutes. The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:34 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:34 <opendevmeet> The meeting name has been set to 'releaseteam' 14:00:37 <ttx> o/ 14:00:42 <hberaud> o/ 14:00:54 <elodilles> \o/ 14:01:36 <elodilles> ok, so pinglist is not needed this time :) 14:01:49 <elodilles> #link https://etherpad.opendev.org/p/yoga-relmgt-tracking 14:01:56 <elodilles> we are @ line 51 14:02:15 <elodilles> and this should be a quick meeting i guess 14:02:28 <ttx> I like quick meetings 14:02:34 <elodilles> :] 14:02:46 <elodilles> let's start with the first topic 14:02:53 <elodilles> #topic Assign next week tasks 14:03:24 <elodilles> I've bravely added myself to the 2nd and 3rd task, 14:03:50 <ttx> I have very limited availability next week so would rather not take on tasks 14:04:06 <hberaud> I can help if you want 14:04:09 <elodilles> ack 14:04:29 <elodilles> maybe I can do task #1 as well and ping hberaud if i need any help 14:04:39 <hberaud> WFM 14:04:47 <elodilles> cool, thanks \o/ 14:05:09 <elodilles> ok, all tasks taken 14:05:22 <elodilles> let's move to the next topic 14:05:32 <elodilles> #topic See tracker for alphabet rollover impact at https://etherpad.opendev.org/p/relmgt-alphabet-rollover-impact 14:05:45 <ttx> Yeah so like we discussed at PTG... 14:05:53 <ttx> I created a list of all our scripts 14:06:10 <ttx> so that we share the work on checking whether they will be affected 14:06:21 <ttx> by the alphabet rollover 14:06:29 <ttx> The answer might well be that none of them do 14:06:38 <ttx> But we need to be thorough about it :) 14:07:01 <ttx> So basically, does the code assume any type of alpha ordering to compare series 14:07:24 <ttx> At this first stage of analysis I'd recommend everyone picks scripts they are familiar with 14:07:26 <hberaud> Could be worth to list the check to do at the begining of this file 14:07:34 <hberaud> checks 14:07:39 <elodilles> ok I'll also try to look into things listed there 14:07:41 <ttx> and marks them OK, KO or UNUSED 14:08:09 <elodilles> hberaud: ++ 14:08:18 <ttx> I dropped a few notes already to show how that looks like 14:08:43 <elodilles> ttx: nice! thanks so far! 14:08:56 <ttx> Note that the list does include code from releases, project-config 14:09:09 <ttx> I added reno at the very end, probably to be reviewed as one unit 14:09:24 <hberaud> ok 14:09:40 <ttx> So let's get through the low-hanging fruit first 14:09:52 <ttx> and keep the tricky ones for the future once we are done to a few to review 14:10:12 <ttx> obviously validate.py will be a big one 14:10:31 <ttx> which we might want to further split reviews of 14:10:37 <hberaud> WFM 14:10:44 <elodilles> ttx: all sounds good! 14:10:50 <ttx> anyway, we have a full cycle to go through that 14:11:01 <ttx> ideally we'd have a good picture by end of Yoga 14:11:31 <ttx> also.. if you can think of code I missed 14:11:47 <elodilles> not right now, but will think on it 14:12:09 <hberaud> +1 14:12:56 <elodilles> ok, cool. so we will see how far we can get with this in Yoga :) 14:13:24 <ttx> that was all. 14:13:37 <elodilles> ok, then last but not least: 14:13:47 <elodilles> #topic Open discussion 14:14:05 <elodilles> anyone? anything else? 14:14:11 <hberaud> nope 14:14:53 <ttx> nope 14:15:19 <elodilles> good 14:15:32 <elodilles> then nothing else remained, just to 14:15:42 <elodilles> #endmeeting