| *** rlandy is now known as rlandy|out | 00:07 | |
| *** ysandeep|sick is now known as ysandeep | 03:48 | |
| *** ysandeep is now known as ysandeep|afk | 04:45 | |
| *** ysandeep|afk is now known as ysandeep | 06:19 | |
| *** jpena|off is now known as jpena | 06:51 | |
| *** ysandeep is now known as ysandeep|lunch | 08:05 | |
| *** ysandeep|lunch is now known as ysandeep | 09:44 | |
| *** rlandy|out is now known as rlandy | 10:28 | |
| *** dviroel|out is now known as dviroel | 11:17 | |
| *** ysandeep is now known as ysandeep|afk | 12:12 | |
| *** dviroel is now known as dviroel|doc_appt | 12:27 | |
| opendevreview | daniel.pawlik proposed openstack/ci-log-processing master: Add Elasticsearch Exporter ansible role https://review.opendev.org/c/openstack/ci-log-processing/+/855875 | 12:32 |
|---|---|---|
| *** dasm|off is now known as dasm | 12:48 | |
| *** ysandeep|afk is now known as ysandeep | 12:49 | |
| *** ysandeep is now known as ysandeep|dinner | 14:28 | |
| *** dviroel|doc_appt is now known as dviroel|doc | 14:46 | |
| *** dviroel|doc is now known as dviroel | 14:46 | |
| jamespage | o/ | 14:55 |
| jamespage | anyone got cycles to get https://review.opendev.org/c/openstack/project-config/+/859219 landed? | 14:55 |
| fungi | jamespage: i went ahead and single-core approved it since it sat a few days without any other core reviewers weighing in. thanks for the reminder | 14:57 |
| opendevreview | Merged openstack/project-config master: charms: add new ceph subteam https://review.opendev.org/c/openstack/project-config/+/859219 | 15:03 |
| jamespage | fungi: thanks! | 15:09 |
| fungi | the deploy jobs for it haven't finished yet (or at least i haven't gotten the notifications for them yet), but should be done shortly | 15:10 |
| *** ysandeep|dinner is now known as ysandeep|out | 15:56 | |
| JayF | I'm looking at Ironic, trying to see what branches need to be EOL'd, and it appears for most old branches; we only have `name-eol` tags, but we have a handful of them that have both `name-em` and `name-eol` tags. | 15:58 |
| JayF | Does this reflect a change in how we approach this, or was something retired improperly in the past? | 15:59 |
| JayF | (all the -em + -eol are 'newer' old branches_ | 15:59 |
| fungi | yes, those are since the introduction of extended maintenance | 15:59 |
| fungi | the process there is that once normal maintenance ends for a branch, the branch state is tagged <series>-em to indicate there will be no further stable point release tags on it | 16:00 |
| JayF | But I'm saying, for some branches; e.g. pike | 16:00 |
| JayF | we have both pike-em and pike-eol tags | 16:00 |
| JayF | oh; I get what you're saying | 16:01 |
| fungi | then when the branch transitions from em to eol state, a <series>-eol tag is made and the branch is deleted | 16:01 |
| JayF | the older releases were **before em branches existed** | 16:01 |
| fungi | yes | 16:01 |
| JayF | thanks :) | 16:02 |
| fungi | in theory, there should be no <series>-eol tag on an existing stable/<series>, the branch should have been deleted once the tag was pushed | 16:02 |
| fungi | but in reality sometimes that got overlooked for various reasons, and should be cleaned up | 16:02 |
| JayF | ack; I'll look at that, right now I was just looking at tags | 16:02 |
| fungi | elodilles has been handling most of the eol-related tasks, so can probably give you a better idea of the overall state and current process | 16:03 |
| *** jpena is now known as jpena|off | 16:05 | |
| JayF | ack; thanks. | 16:05 |
| JayF | Trying to get a view of the landscape for ironic; get releases for all our stable/bugfix releases that are eligible to be released and EOL branches we don't backport things to anymore | 16:06 |
| elodilles | there are some branches that are tagged as *-eol but not deleted, but those are not ironic ones afair | 16:27 |
| elodilles | * not deleted yet | 16:27 |
| elodilles | (i wanted to wait for the last couple of pike branches to get tagged with pike-eol before running the cleanup script | 16:28 |
| elodilles | ) | 16:28 |
| *** chkumar|rover is now known as raukadah | 17:15 | |
| JayF | Hmm. I'm getting autoresponders to *my* (not list email) from someone on the list. Is that OK? Do we pull folks from the list for that like we do if it went to the list? | 18:09 |
| clarkb | JayF: is that because they are accepting your meeting invites? | 18:44 |
| JayF | clarkb: no, it's all chinese that translates to "I have received your email and will respond soon" | 18:45 |
| clarkb | or "accepting" them. Basically I wonder if that is a weird interaction with the ics files and wouldn't normally happen | 18:45 |
| JayF | and I got them for multiple emails; not just the ones in that TC PTG thread | 18:45 |
| clarkb | interesting the emails should have reply-to's set for the list. Still likely broken client software, but ya that may be worth temporarily removing from the list for | 18:46 |
| clarkb | fungi: ^ | 18:46 |
| JayF | I will happily DM the from: address for these emails to whomever is appropriate | 18:46 |
| clarkb | fungi is the list admin for openstack-discuss so is the most appropriate person | 18:48 |
| fungi | JayF: yeah, give me the addresses via privmsg and i'll set their subscriptions to nomail if they're sending from the subscribed addresses | 18:52 |
| *** dviroel is now known as dviroel|afk | 19:42 | |
| *** lifeless_ is now known as lifeless | 20:14 | |
| *** dviroel|afk is now known as dviroel | 20:52 | |
| *** tosky_ is now known as tosky | 21:24 | |
| *** dasm is now known as dasm|off | 21:24 | |
| *** rlandy is now known as rlandy|out | 22:10 | |
| *** ysandeep|out is now known as ysandeep | 23:58 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!