| *** mhen_ is now known as mhen | 01:32 | |
| opendevreview | Merged openstack/devstack master: Bump etcd to 3.25.x https://review.opendev.org/c/openstack/devstack/+/952755 | 05:12 |
|---|---|---|
| *** elodilles_pto is now known as elodilles | 07:54 | |
| opendevreview | Stephen Finucane proposed openstack/devstack master: Remove dead checks for Python 3.6 https://review.opendev.org/c/openstack/devstack/+/956765 | 09:59 |
| opendevreview | Stephen Finucane proposed openstack/devstack master: Remove dead checks for Fedora 36 https://review.opendev.org/c/openstack/devstack/+/956766 | 09:59 |
| opendevreview | Stephen Finucane proposed openstack/devstack master: Remove dead checks for Fedora 36 https://review.opendev.org/c/openstack/devstack/+/956766 | 12:37 |
| opendevreview | Merged openstack/devstack master: Replace use of fgrep https://review.opendev.org/c/openstack/devstack/+/956652 | 12:50 |
| opendevreview | Merged openstack/devstack master: Fix default settings for Ubuntu aarch64 https://review.opendev.org/c/openstack/devstack/+/956646 | 12:56 |
| opendevreview | Merged openstack/devstack stable/2025.1: Fix uninialized os_VENDOR https://review.opendev.org/c/openstack/devstack/+/956620 | 13:08 |
| opendevreview | Merged openstack/devstack master: Remove dead checks for Python 3.6 https://review.opendev.org/c/openstack/devstack/+/956765 | 13:39 |
| opendevreview | Douglas Mendizábal proposed openstack/devstack master: Set password regex for security compliance https://review.opendev.org/c/openstack/devstack/+/956111 | 15:05 |
| *** gthiemon1e is now known as gthiemonge | 15:56 | |
| opendevreview | Douglas Mendizábal proposed openstack/devstack master: Set password regex for security compliance https://review.opendev.org/c/openstack/devstack/+/956111 | 16:33 |
| sean-k-mooney | gmaan: so looking at the devstack launchpad im not seeing a bug team configured so its default back to the project maintainers/driver group | 18:13 |
| sean-k-mooney | shoudl there be an open bug team for it? | 18:13 |
| sean-k-mooney | i mean its not really activly used i was just looking at a bug refence wehn doing a review an dwas going to triage it | 18:14 |
| gmaan | checking | 18:21 |
| sean-k-mooney | its not urgent i was just surpised | 18:21 |
| gmaan | yeah, we did not have or I will say required to have a separate bug team so used driver team only | 18:24 |
| gmaan | but I think we can keep it same until we have more people triaging bugs than who are in driver team | 18:25 |
| sean-k-mooney | ack no worries | 18:25 |
| gmaan | in that case, i think I should add sean-k-mooney and tosky in devstack-driver team also https://launchpad.net/~devstack-drivers/+members | 18:25 |
| gmaan | dansmith: frickler clarkb ^^ any objection on that | 18:26 |
| sean-k-mooney | that fine but its more permsions then i strictly need | 18:26 |
| dansmith | *shrug* | 18:26 |
| sean-k-mooney | thats why i ask about the bug team. honestly im fine either way | 18:26 |
| clarkb | no objection | 18:27 |
| gmaan | I will cleanup this to have current active core members, and same for termpest too which is very out of dated | 18:30 |
| frickler | fine for me, I don't think we need to split the team | 18:32 |
| gmaan | ++ | 18:34 |
| gmaan | done | 18:38 |
| sean-k-mooney | since we are on this topic i notice that devstacck is not really using series. want me to fix that when i do it for watcher or will i just leave it as is | 18:40 |
| sean-k-mooney | devstack is obviously branhced but is it technially release with intermediaries or is it a differnt release model? | 18:41 |
| sean-k-mooney | those are not stictly related im just wondering if we need to target bugs/patchs across brnahces often or is that over kill | 18:42 |
| sean-k-mooney | ah its release-model: untagged | 18:43 |
| sean-k-mooney | and stable-branch-type: tagless | 18:43 |
| gmaan | i will say it was overkill due to small team. we do release devstack every cycle and new stable branch is created but do not track/target bugs per release. usually those are fixed on master and backported always | 18:46 |
| sean-k-mooney | ack, i dont think we nessiarlly need it i was just trying to figure out the best way of work so im fine with "doing more useful work over tracking the useful work" | 18:47 |
| gmaan | triaging bugs to critical or high and fixing/merging them is our main tracker for devstack bugs and everything else on wishlist or good if anyone propose fix and we review | 18:47 |
| gmaan | yeah | 18:48 |
| sean-k-mooney | ya so normally as part of +2ing things i look at the tracker link assumign it has one and if its a bug i target it to the relevent stable branches if its backportabel and set the other triaged fields. | 18:48 |
| sean-k-mooney | im fine with skipign the extra bits | 18:50 |
| gmaan | yeah | 18:50 |
| sean-k-mooney | i mainly do that as part of the code review because i will forget otherwise | 18:50 |
| gmaan | in most cases, there will be backport at same time on master or sooner when we see fix needed for stable branch jobs also | 18:51 |
| gmaan | but good to check while review | 18:51 |
| sean-k-mooney | i assume devstack follow normal stable branch policy and does not do "feature" backports in general | 18:52 |
| sean-k-mooney | for example the centos 10 stream supprot | 18:53 |
| gmaan | yup, | 18:53 |
| sean-k-mooney | cool | 18:53 |
| sean-k-mooney | i know some installer that wont be named were a bit loose with that role or flat out ignored it | 18:54 |
| sean-k-mooney | s/role/rule/ | 18:54 |
| gmaan | the key thing we check 'where it is needed or tested' to particular stable branch and any new features/configurations which are implemented/tested on master and did not backported on service side, does need to be backported in devstack stable branch also | 18:57 |
| gmaan | basically not very strict on backport and go with the flow of how services side fix/implementation are backported | 19:09 |
| sean-k-mooney | ack, ya if a service shiped a feature lst cycle but didnt have devstack suppport or tempest coverage i could see backporign that supprot if they wanted to test it in a stabel branch but that probaly is an excption to the norm | 19:28 |
| gmaan | yeah | 19:33 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!