| frickler | rosmaita: repeating here as you don't seem to be in #openstack-infra: IMO it would be a good idea to create #openstack-unmaintained as a pendant to #openstack-stable and also channel all the gerritbot messages there | 15:34 |
|---|---|---|
| frickler | maybe you want to look into that? | 15:34 |
| rosmaita | maybe ... i didn't even know there was an #openstack-stable | 15:35 |
| frickler | ah, ok, well that's kind of the home for the stable team and gets bot messages whenever a review is proposed against a stable branch | 15:36 |
| frickler | also just ftr mnasiadka has now proposed unmaintained-core groups for the kolla team similar to what ironic did https://review.opendev.org/c/openstack/project-config/+/908321 | 15:38 |
| fungi | i guess i'll restate what i said in #openstack-infra in response too. i have no problem with the suggestion to create a #openstack-unmaintained channel *if* there are people who feel like they're going to join and make use of notifications there. otherwise i don't see the point | 15:43 |
| fungi | the way we've set up the unmaintained branch process/policy, i expect it to mostly just be a short-lived limbo state between end of normal maintenance and eol. older stable branches already tend to get ignored, so it'll probably be rare that unmaintained branches get much attention or opted into subsequent cycles before they're deleted | 15:45 |
| rosmaita | (apologies ... i am in a meeting an not at all paying attention here) | 15:46 |
| frickler | ah, sorry for splitting the discussion. for me one benefit beside the bot notification would be to have something to direct people to in order to reduce discussions in the project channels. but yeah, maybe wait a month or two and see if the issue goes away on its own ;) | 15:47 |
| fungi | if there are people to direct somewhere (and if they'll actually take advantage of it) then sure, no problem | 15:48 |
| fungi | i mostly just want to avoid the "build it and they will come" mentality we used to fall victim to | 15:48 |
| fungi | a good initial default would simply be to make sure we don't spam project channels or #openstack-stable with notifications about unmaintained/.* branches unless they actually want them. we don't *have* to send any notifications about things related to unmaintained branches, that's sort of the definition of unmaintained after all | 15:50 |
| frickler | yes, afaict most notifications filter for stable/* currently, so that's fine for now | 15:51 |
| frickler | let's do this, I just joined the channel and thus created it, and I can then also send people there. and I'll watch what happens and register the channel officially once any significant activity happens | 15:52 |
| fungi | wfm, thanks! | 16:03 |
| rosmaita | frickler: ty, sounds good | 16:09 |
| frickler | elodilles: tonyb: mnasiadka: ^^ fyi (see the last ten lines or so) | 16:13 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!