Thursday, 2026-03-19

opendevreviewchandan kumar proposed openstack/watcher-specs master: Add spec for improving watcher-dashboard testing  https://review.opendev.org/c/openstack/watcher-specs/+/97022007:25
opendevreviewchandan kumar proposed openstack/watcher-specs master: Add spec for improving watcher-dashboard testing  https://review.opendev.org/c/openstack/watcher-specs/+/97022007:29
opendevreviewTakashi Kajinami proposed openstack/watcher-tempest-plugin master: Add stable/2026.1 job  https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/98122008:45
opendevreviewchandan kumar proposed openstack/watcher stable/2026.1: Add watcher-grenade-skip-level-always job  https://review.opendev.org/c/openstack/watcher/+/98122510:24
dviroelhi folks, heads up, watcher meeting will start in 9 min, here in this channel11:51
dviroelfeel free to add you own topics to the meeting etherpad: https://etherpad.opendev.org/p/openstack-watcher-irc-meeting11:51
dviroel#startmeeting watcher12:00
opendevmeetMeeting started Thu Mar 19 12:00:33 2026 UTC and is due to finish in 60 minutes.  The chair is dviroel. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
opendevmeetThe meeting name has been set to 'watcher'12:00
amoralejo/12:00
dviroelhi o/ who is around today?12:00
chandankumaro/12:01
jgilabero/12:01
dviroelcourtesy ping:  sean-k-mooney rlandy12:01
dviroelhi everyone o/12:02
dviroellet's start with today's meeting agenda12:02
dviroel#link https://etherpad.opendev.org/p/openstack-watcher-irc-meeting#L25 (Meeting agenda)12:02
dviroelas usual, feel free to add your own topics to the agenda12:02
dviroelwe also have a topic for reviews and bugs, if you want to discuss any, feel free to add there12:03
dviroel#topic Release Schedule12:03
rlandyo/12:03
dviroel#link https://releases.openstack.org/gazpacho/schedule.html12:03
dviroelwe are at R-2 week12:04
dviroelnext week is our final week to propose new RCs, if any12:04
dviroelso far, i only see one issue with the watcher-dashboard12:04
dviroelthere was an update in the requirements that broke our dashboard12:05
dviroel#link https://github.com/openstack/requirements/commit/c4bfeb4d265ef6e34b2228387118aed32af8530912:05
chandankumarit is broken on RDO only i think12:05
dviroelthe most recent version of Static-Font-Awesome renamed some css files12:05
amoralejso we need https://review.opendev.org/c/openstack/watcher-dashboard/+/980533 12:06
dviroelwe merged a fix that was proposed12:06
dviroel#link https://review.opendev.org/c/openstack/watcher-dashboard/+/98045612:06
dviroelyeah, but 2026.1 is still broken12:06
chandankumarWe are not sure anyone is going to update the version of XStatic-Font-Awesome in RDO side12:06
dviroelif we look at 2026.1 patches12:07
dviroel#link https://review.opendev.org/c/openstack/watcher-dashboard/+/98041412:07
dviroelfor instance, you will see that is failing on CI12:07
dviroelso we will need to get this backported, and request a new release for the dashboard12:07
amoralejyep12:08
dviroelamoralej: yeah, this is the backport12:08
dviroelchandankumar: yeah, the rdo side is anothe issue12:08
amoralejrequirements project is not branched yet12:08
amoralejso master applies to 2026.1 i guess12:08
dviroelthere was many updats proposed to the requirements in the past weeks12:08
dviroeli do belive so, otherwise it will break horizon then :) 12:09
amoralejyep :)12:09
dviroelsince they also removed their workaround to work with both current and previous version of the package12:09
amoralejthe change in horizon was backported to 2026.1 ?12:09
dviroelamoralej: i think that merged before the release12:10
dviroelthis is the patch12:11
dviroel#link https://review.opendev.org/c/openstack/horizon/+/97900912:11
chandankumaryes, we need that backport all the release 2026.1 specific patches https://review.opendev.org/c/openstack/watcher-dashboard/+/980415 jobs are broken due to compressor.exceptions.UncompressableFileError: 'horizon/lib/font_awesome/css/font-awesome.css' could not be found in the COMPRESS_ROOT '/tmp' or with staticfiles.12:11
amoralejyep, that's in 2026.112:11
amoralejso, let's merge the backport12:11
dviroelfor the records12:12
dviroel#link https://github.com/openstack/releases/blob/master/deliverables/gazpacho/horizon.yaml12:12
dviroelthis is the commit, which includes the previous change 12:12
dviroelso yeah, we will need to backport12:13
amoralejactually, it mentions the fontawesome think even in the highlights12:13
dviroeli will reach the cores to get that merged today/tomorrow12:13
dviroelamoralej: true12:13
dviroelany other concern with that?12:14
chandankumarnope12:14
dviroelok, moving on12:14
dviroel#topic Core team updates12:14
dviroelI sent an email to openstack-discuss mailing list past friday with a proposal for watcher core team updates12:14
dviroelthe removals is a follow up from previous actions wrt core team cleanups, mainly for core maintainers that are no longer active in watcher repos12:15
dviroelthose listed were already removed from core-groups, as mentioned in the email, but they will always be welcome back if they want to continue contributing with the project12:15
dviroeland note that, there is also a core addition proposal12:15
dviroelI also proposed to add amoralej to both watcher-core and watcher-dashboard groups12:16
dviroelamoralej has a good amount of high quality reviews in most of our repos as also help us a lot maintaining the project healthy 12:16
chandankumar+1 to the proposal12:16
dviroelamoralej: thanks for accepting 12:16
amoralejThank you for your trust :)12:16
chandankumaramoralej: helped a ton in reviewing in watcher-dashboard patches12:16
dviroelif you all agree with that, and since there is no concerns/feedbacks in the ML, i will proceed with adding amoralej to these groups after we close this meeting12:17
jgilaber+1 to all, it'll be great to have amoralej in the core team!12:17
dviroelgreat! since there is no objection, i will proceed with that :) 12:18
amoralejthanks!12:18
dviroel#agreed adding amoralej to the proposed core groups12:18
dviroelamoralej++12:18
dviroelalright, next topic 12:19
dviroel#topic PTG Topics and slots proposal12:19
dviroelI would like to add a initial proposal for our ptg12:19
dviroeland book some slots for us, so other teams can also book theirs to avoid conflicts (e.g. cyborg)12:20
dviroelwe can change that at any time before the PTG too12:20
dviroelI would initially propose12:20
dviroelWed (22th) and Thu (23th): 12:00 UTC - 16:00 UTC12:20
dviroelthis is April ^, ok :) 12:20
dviroelas have Fri as backup if needed12:21
dviroelI would be also extending for an 1h, compared to the previous PTG12:21
dviroeli am intentionally skipping tuesday due to a national holiday, but I am ok with joining on a Tuesday too if the team prefers12:21
amoralejyep, last time we were short of time, i think, good to extend12:21
dviroelwe should also take care to not take too much time in some topics, so we can at least cover more stuff12:22
dviroelpart of the wathcer team will divide its attention with other teams12:22
dviroellike nova, cyborg12:22
dviroelwhat do you folks think?12:23
dviroelwe can always revisit the allocation too12:23
dviroelwe may book some time in monday too, if we want, just to run a quick retro12:24
sean-k-mooneyo/12:24
jgilaberI think it's reasonable, I don't think we have dates set for cyborg and I don't know about nova12:24
jgilaberwhich I think will be the most likely sources of conflicts for our team12:24
amoralejwed + thu lgtm12:24
dviroelsean-k-mooney: hey o/12:24
dviroelalready, that said, i can initially book both days for watcher, and we can sync with other teams later12:25
chandankumarlooks good for wed and thu, timing works for me also.12:25
dviroel++12:25
jgilaber+112:25
dviroelok, we can sync again in a few weeks about that12:25
dviroelright now i would just ask folks to start adding topics to our PTG etherpad12:26
dviroel#link https://etherpad.opendev.org/p/watcher-2026.2-ptg12:26
dviroelok, one more topic that I want to quick cover12:27
dviroel#topic OpenInfra Live - Gazpacho release12:27
dviroelthere was a mail in the ML last week12:27
dviroel#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/XSMMR2KF5PHACXXD4UCDCETKCYT4UJ3Q/#N2A5BQACADL4RNSYA7JSCJLSFO577DFM12:27
dviroelthe OpenInfra Live will happen on Thursday, April 2 at 1400 UTC12:27
dviroelIt is a webinar in the openinfra youtube channel that we can present the highlight of openstack projects 12:28
dviroelI will be presenting the watcher highlights for gazpacho release12:28
dviroelit seems that it might be holiday in a couple of countries12:29
dviroelbut if you miss it, you can still watch the recording afterwards in their channel12:29
dviroelok, that's it for the topic12:30
dviroelmoving to the next one then12:30
dviroel#topic Reviews12:30
dviroelI proposed a follow up change in the eventlet-removal topic12:30
dviroel#link  https://review.opendev.org/c/openstack/watcher/+/980818 (Make native threading the default concurrency mode) 12:31
dviroelto make threading mode as default in 2026.2 release12:31
dviroelwith that patch, jobs that were running in eventlet mode, now will run in threading mode12:31
dviroeland the unit and tempest one that were in threading mode, will now run in eventlet mode12:32
dviroelWe still have the option to switch between modes using the flag, but now it defaults to disable eventlet12:32
dviroelplease review when you have some time12:33
amoralejeventlet switch has been great work dviroel++ I think it's good to change the defaults early in the cycle12:33
dviroelthanks amoralej!12:33
sean-k-mooney+1 to updating the default early12:34
dviroeli also have a DNM patch (which I will rebase/update) that validates the code removal too, just in case you folks want to take a look12:34
sean-k-mooneyto let it bake in ci for as long as possible12:34
dviroelack, we will keep 2 jobs still testing eventlet, to avoid any breakage that may occur in the way12:35
dviroelalright, moving to next reviews12:35
dviroelthese are specs proposed for 2026.2 cycle12:35
dviroel#link https://review.opendev.org/c/openstack/watcher-specs/+/969840 (Audit Pipeline)12:35
dviroelwe discussed a lot about that in 2026.1 cycle, with tons of reviews (thanks all for that)12:36
dviroelI have been playing locally with a small PoC of the proposal12:36
dviroeli have already made some updates to the spec based on that, like more detailed section about the mutable data cluster and the metric data cache12:36
dviroelthe updated was pushed yesterday12:37
dviroelah, and the work items section was also updated to provided a better phased development12:37
sean-k-mooneyhave you started any POCs or practical explortatiosn of the work?12:37
sean-k-mooneyi assume the addtion of the parmater ot the audit templeate would be one fo the first steps12:38
dviroelsean-k-mooney: I have a workable PoC at this moment, an audit pipeline with 2 stages (a zone_migration + workload_stabilization)12:38
sean-k-mooneyack, i think the defautl_parmaters part is not contovertial and could/shoudl likely be the first chagne actully pushed for this since it really does not depend on the details fo the rest12:39
dviroel++12:39
sean-k-mooneyi have not looked at this since december so i have not loaded context but i think we should proably try and review it over the next week or 312:40
dviroelack, thaks12:40
sean-k-mooneyif we are in general agreement i dont think this nessisarly need to be a ptg topic but fi we still have open questions it could be12:40
dviroelwe can discuss in more details in the following weeks, and if needed we can discuss more details in the ptg12:41
sean-k-mooneyor we  coudld do a one of gmeet instaead of oen of these meetings12:41
dviroel++12:41
amoraleji will review the last PS12:41
dviroelthis is a good idea12:41
dviroelwe can use part of the weekly meeting and discuss in a gmeet 12:41
* dviroel will be on pto for 2 weeks, we can schedule a session early in april12:42
amoralej+1 for gmeet out of ptg12:42
sean-k-mooneyack12:42
dviroelone detail in the spec12:42
dviroeli removed the audit trigger from it12:43
dviroelsince the spec was growing, i decided to remove the Audit Trigger piece, which will have it's own spec proposed still for 2026.2 cycle12:43
dviroeli think that it is better this way, but I also accept feedbacks12:43
dviroelwritting a spec only for the trigger since it will touch more places than I was expecting initially12:44
dviroeli may poc only the trigger part too12:44
dviroelto validate it12:44
sean-k-mooneyok12:45
dviroeland we can decide on implementing if first or later, we shall discuss in the following weeks12:45
dviroelbut it is on my backlog here12:45
dviroelok, next review then12:45
dviroel#link https://review.opendev.org/c/openstack/watcher-specs/+/970220 (Add spec for improving watcher-dashboard testing)12:46
chandankumarI have added this one12:46
chandankumarthank you everyone for all the reviews, I have addressed most of them12:47
chandankumarSince master is open now. I would like get feedback on this and get merged12:47
chandankumarWe have the playwright poc and skip action integration patch also up based on the spec12:48
dviroelchandankumar++ thanks, yes, and is a spec that was alredy discssued and validated with PoCs 12:48
chandankumarI will propose the requirements patch to add playwright once spec is merged12:48
sean-k-mooneyim wondering if i shoudl convert https://review.opendev.org/q/topic:%22service-layer-pattern%22 into a spec and or how to make sure it does not conflict with that work12:48
sean-k-mooney^ was part of https://review.opendev.org/c/openstack/watcher-specs/+/96343812:48
sean-k-mooneyor at leat it implemntn part of ^12:49
sean-k-mooneybut it goes beyond that12:49
sean-k-mooneywe likly can aprpove your spec indepmendently12:49
sean-k-mooneybut there is a stong overlap as that is removeing selenium and doing the refactor of the test layout12:50
dviroelsean-k-mooney: it would be good to have it documented in a spec12:50
sean-k-mooneyright the documentiaotn is currently in the first patch https://review.opendev.org/c/openstack/watcher-dashboard/+/978239/3/doc/source/contributor/service-layer-pattern.rst12:51
dviroeloh ok, so a spec may only duplicate things12:51
sean-k-mooneyi created a set of contibutor docs as the first patch to distial feedback i raised in a number of reviews12:52
sean-k-mooneywell yes and no12:52
sean-k-mooneyim kind of doing 3 thing in that serise12:52
sean-k-mooney1 the adoption of ruff12:52
sean-k-mooney2 the spliting of the test direcotres to make room for future testing12:52
sean-k-mooneyand 3 docuemntign and implementign the service layer pattern12:52
chandankumar2 is covered in integration test spec12:52
dviroel1 and 2 may not need a spec I guess12:53
sean-k-mooneyyes but it was also covered by the spec form the last cycle https://review.opendev.org/c/openstack/watcher-specs/+/970220/12/specs/2026.2/approved/improve-watcher-dashboard-ui-testing.rst12:53
chandankumar3 would be good to have a spec12:53
sean-k-mooneyso ya i ll factor 3 out into a spec 12:53
dviroel+112:53
amoralejbut i like the idea of keeping the contributor guide12:53
sean-k-mooneywhat i was going to propose is pulling 1 and 2 out into the very start of my series12:54
amoralejso spec would be a summary?12:54
sean-k-mooneyi.e. the ruff and test directoy refactor12:54
sean-k-mooneythat will remove the confilcit12:54
sean-k-mooneythen have a spec to detial the design pattern12:54
sean-k-mooneyamoralej: kind of yes it woudl capture why it hink we shoudl be adopting this and an overview12:55
amoralejgood12:55
sean-k-mooneyand then the contibotr docs woudl have the details as it applies to this project12:55
dviroellgtm12:55
sean-k-mooneyso basiclly im proposing this https://review.opendev.org/c/openstack/watcher-dashboard/+/978258/3 and the 2 patchs before it shoudl be merged soon12:56
sean-k-mooneyand then there will be no conflict12:56
sean-k-mooneyi need ot redo the isort one12:56
sean-k-mooneyand ill file a spec for the rest seperately and chandan can proceed withthe playwritght work12:56
dviroelalright, thanks for the hard work there sean-k-mooney 12:57
sean-k-mooneychandankumar: if that works for you ill pull the 3-4 patches out onto master cleanly later today and then you can build your work on top12:57
sean-k-mooneychandankumar:does that sound ok?12:58
chandankumarworks for me12:58
dviroelgreat12:59
sean-k-mooney1 ruff isort, 2 ruff format, 3 test resutcre ,4 selenium deletion 5 your stuffs 12:59
dviroelif you two agree, works for me too12:59
sean-k-mooneywe can likely review/approve your spec in the next few days13:00
sean-k-mooneydviroel: when will you be on pto is it form tomorow?13:00
dviroelmy last day before pto is tomorrow13:00
sean-k-mooneyack so i guess unless you want to review it specificlly ill review it with jgilaber and or amoralej if you proceed with thte core addtion before you leave13:01
dviroelsure, that works13:01
dviroellet me quickly link the next spec too13:02
dviroel#link https://review.opendev.org/c/openstack/watcher-specs/+/97889713:02
dviroel(Add 2026.2 OpenStackSDK migration spec for remaining services) 13:02
dviroelsince we are out of time13:02
dviroeljgilaber: a quick summary of this one13:02
jgilabersure13:02
dviroelI think that most of us already know, but it is good for the records :)13:03
jgilaberI reproposed last cycle's spec but updating with what I would like to do this cycle13:03
jgilabermoving the kesytone, ironic, placement and cinder helpers to use openstacksdk like we did for the nova helper13:03
dviroel+113:04
dviroelgreat work that you did with nova migration to openstacksdk13:04
jgilabermy only question really is if I should create a new blueprint or reuse the same one13:04
dviroela single one might be easier to track the overall migration, in future13:05
dviroeli think that we continue with the same one13:05
dviroelbut we may have other opiniions in the spec13:05
dviroelwe have to close this meeting13:06
dviroelbut before that13:06
jgilaberthat was thinking as well so I think we're set for now. I added the topic for the PTG, we can either have a really short discussion or skip it13:06
dviroel#topic Volunteers to chair next meetin13:06
sean-k-mooneynormally we woudl ahve 1 per cycle13:06
amoralejI can take it13:06
sean-k-mooneyand just add part-213:06
sean-k-mooneyectra13:06
sean-k-mooneybut either is fine13:06
dviroelamoralej: thanks!13:06
dviroelamoralej: please check if April 2nd you will have enough people, otherwise you may want to cancel that meeting, during next meeting :) 13:07
dviroelalright, thanks everyone13:07
amoralejactually, i will also be out on apr 2nd13:07
amoralejwe can discuss it next week, yep13:08
dviroelexaclty13:08
dviroeljgilaber: may be out too13:08
dviroelok13:08
dviroellet's wrap up for today13:08
jgilaberyep I'll be out as well13:08
dviroelwe will meet again next week13:08
dviroelthank you all for participating13:08
dviroel#endmeeting13:08
opendevmeetMeeting ended Thu Mar 19 13:08:39 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:08
opendevmeetMinutes:        https://meetings.opendev.org/meetings/watcher/2026/watcher.2026-03-19-12.00.html13:08
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/watcher/2026/watcher.2026-03-19-12.00.txt13:08
opendevmeetLog:            https://meetings.opendev.org/meetings/watcher/2026/watcher.2026-03-19-12.00.log.html13:08
dviroelsean-k-mooney: hey since you are around, can you check the issue in watcher-dashboard, we discussed earlier in the meeting: https://meetings.opendev.org/meetings/watcher/2026/watcher.2026-03-19-12.00.log.html#l-1713:09
dviroelsean-k-mooney: we need to approve the dashboard backport to 2026.113:10
sean-k-mooney is it the font awsome one13:10
dviroelyep13:10
sean-k-mooneybecause i tought i approved that at the weekend13:10
dviroelsean-k-mooney: you approved in master13:10
sean-k-mooneyoh the backport right13:10
dviroelyeah13:10
dviroel2026.1 is broken13:10
sean-k-mooneyok ill look at that shortly13:10
dviroelthanks!13:10
sean-k-mooneylooks like it failed on pep813:11
sean-k-mooneycompressor.exceptions.UncompressableFileError: 'horizon/lib/font_awesome/css/font-awesome.css' could not be found in the COMPRESS_ROOT '/tmp' or with staticfiles.13:11
dviroelwhich patch are u looking? 13:12
sean-k-mooneyoh sorry13:12
dviroelhttps://review.opendev.org/c/openstack/watcher-dashboard/+/98053313:12
sean-k-mooneywrach link13:12
sean-k-mooneyhttps://review.opendev.org/c/openstack/watcher-dashboard/+/98041513:12
sean-k-mooneyi was looking at the bot patches13:12
sean-k-mooneywhich are failing on the lack of your patch link13:12
dviroelright13:12
sean-k-mooneyjgilaber: is there aa reason your only +1?13:13
sean-k-mooneyasking before i add +2w13:13
dviroeljgilaber: is not in the dashboard core13:13
dviroelsean-k-mooney: ^13:13
sean-k-mooneyoh right13:13
sean-k-mooneyok ill merge that so and amoralej will be on that team soone anyway 13:13
sean-k-mooneyso we will have coverage13:13
dviroel++13:13
dviroelyes13:14
sean-k-mooneyonce that is in ill recheck the bot patches and approve them if they pass13:14
sean-k-mooneyactully let me just rebase them 13:14
dviroelsean-k-mooney: that merged, we will need to request a new rc for dashboard13:14
opendevreviewOpenStack Release Bot proposed openstack/watcher-dashboard stable/2026.1: Update .gitreview for stable/2026.1  https://review.opendev.org/c/openstack/watcher-dashboard/+/98041413:15
opendevreviewOpenStack Release Bot proposed openstack/watcher-dashboard stable/2026.1: Update TOX_CONSTRAINTS_FILE for stable/2026.1  https://review.opendev.org/c/openstack/watcher-dashboard/+/98041513:15
dviroel++13:15
sean-k-mooneyyes that unfortuneate but it happens13:15
sean-k-mooneyespcially when our depencies get a requirement freeze exception13:16
sean-k-mooneyjgilaber: chandankumar  since ye are the desigated release liasons can ye follow up with the RC2 release patch once its fixed13:17
dviroel:)13:17
opendevreviewMerged openstack/watcher-dashboard stable/2026.1: Fix fontawesome.css patch  https://review.opendev.org/c/openstack/watcher-dashboard/+/98053313:27
dviroelamoralej: you have been added to the core groups mentioned in the meetings/email13:28
dviroelamoralej: you can test it here https://review.opendev.org/c/openstack/watcher-dashboard/+/980414 :) 13:28
amoralejdviroel, it's working fine :)14:05
dviroel\o/14:06
jgilabersean-k-mooney, I can propose the patch for the rc214:16
sean-k-mooneyack jgilaber you may or may not want to wait for https://review.opendev.org/c/openstack/watcher-dashboard/+/980415/2 to merge14:18
opendevreviewMerged openstack/watcher-dashboard stable/2026.1: Update .gitreview for stable/2026.1  https://review.opendev.org/c/openstack/watcher-dashboard/+/98041414:18
sean-k-mooneyits not actully requried for the rc but that the last patch i expect us to merge until after the release14:19
jgilabersure, no reason to not wait for a bit and have that in, I can prepare the patch in the meantime and send it when this lands14:20
sean-k-mooneyshould be merged in less than an hour14:20
opendevreviewMerged openstack/watcher-dashboard stable/2026.1: Update TOX_CONSTRAINTS_FILE for stable/2026.1  https://review.opendev.org/c/openstack/watcher-dashboard/+/98041514:31
dviroeljgilaber: thanks jgilaber 14:32
jgilaberthat merged faster than expected :) I submitted the rc2 patch https://review.opendev.org/c/openstack/releases/+/98129314:35
jgilaberdviroel, I guess it will need your +1 as PTL14:35
dviroeljgilaber: thanks, lgtm, checked the commit hash and matches14:46
dviroeljgilaber: still not the official ptl yet, but they know that you/chandan are still the release liasons also14:47
sean-k-mooneyjgilaber: os actully dviroel  does not need too14:59
sean-k-mooneyif you are set as the release liason properly then ptl-approved shoudl be set15:00
sean-k-mooneybut we might need to go update that properly in the release rpo15:00
sean-k-mooneyits sotread in a diffent localtion for ptl projects15:00
sean-k-mooneyye need to be listed here https://github.com/openstack/releases/blob/master/data/release_liaisons.yaml15:00
dviroelthat would be my first task as ptl15:03
dviroelsince we reset the dpl model, we don't have any other place saying who are our release liaisons15:04
dviroelbut that's fine, would not block the release patch to get merged15:05
sean-k-mooneyim going to have to update this for cyborg as well if you dont get time for this before you go on pto i can just do one patch for both15:06
dviroellet me see iirc, we decided to have both jgilaber and chandankumar as release liaisons on both projects, but they would focus more on one each?15:08
sean-k-mooneyyep15:11
sean-k-mooneybasically so each is the others backup and you and i as ptl will be the secondary backup15:11
sean-k-mooneythe ptl still are emporwed to do the release even if we have liasons nominated to do that15:12
jgilaberyes, that was the idea dviroel 15:16
dviroelack, going to prepare the patch - thanks15:17

Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!