| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-manuals master: Add OpenStack-Ansible to 2025.1 deploy guides https://review.opendev.org/c/openstack/openstack-manuals/+/953312 | 13:50 |
|---|---|---|
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-manuals master: Add kolla to deployment guide page https://review.opendev.org/c/openstack/openstack-manuals/+/953313 | 13:55 |
| frickler | noonedeadpunk: thx for ^^. tkajinam: puppet should also be ready? I don't want to have it look like we forget about you ;) | 14:14 |
| noonedeadpunk | I side-tracked a little bit after pushing these 2 for renos link, sorry | 14:16 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-manuals master: Add Puppet to deployment guide page https://review.opendev.org/c/openstack/openstack-manuals/+/953317 | 14:18 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-manuals master: Add Puppet to 2025.1 deployment guide page https://review.opendev.org/c/openstack/openstack-manuals/+/953317 | 14:19 |
| tkajinam | frickler, unfortunately we do not have what can be called deployment guide (our guide focus on explaining modules and we do not provide the steps to actually deploy a cluster) so leave puppet now. I can provide add something (even short), probably. | 14:20 |
| frickler | tkajinam: looks like ^^ only sets "has_install_guide: true" instead of deploy guide. waiting on your review before approving | 14:23 |
| tkajinam | ah yes. | 14:23 |
| tkajinam | frickler, another question... puppet-openstack-guide repo is branchless ( I thought to switch it to branch mode but haven't done it). Can we add it to 2025.1 doc or should we keep it only in latest doc ? | 14:25 |
| tkajinam | if adding the link there is ok I have no objection. | 14:26 |
| frickler | tkajinam: well I guess it depends on how stable the docs are ... like are they expected to still work for 2025.1 in a year or two? (at least while it is expected to be a supported release) | 14:28 |
| frickler | would be bad if we had to drop the link in a cycle because the docs got updated to work only for the next release | 14:28 |
| tkajinam | ERROR has_install_guide set for puppet-openstack-guide but https://docs.openstack.org/puppet-openstack-guide/2025.1/install/index.html does not exist (404) | 14:31 |
| tkajinam | it seems the tool requires the exact branch | 14:31 |
| tkajinam | frickler, it is mostly stable though we expect some updates soon due to c9s->c10s migration... | 14:31 |
| tkajinam | maybe we can abandon it now and I'll try to consider some plans to have doc for each branch somehow | 14:32 |
| frickler | yeah, in theory we could add a redirect from the above to latest, but it will be difficult to keep that reasonably uptodate I guess | 14:33 |
| mnaser | i _really_ _really_ dont want to give up on pushing to land stuff upstream before we push them downstream, so i want to keep pushing on how we can maek things better upstream. | 19:52 |
| mnaser | for example, https://review.opendev.org/q/I43fd10d5ae220450afc584a0f6fd40eb95ec8134 has been open since april 14th | 19:52 |
| mnaser | and they're cleanly applied backports | 19:53 |
| mnaser | https://review.opendev.org/q/project:openstack/ovn-bgp-agent+status:merged meanwhile the project has been merging other things since then too.. | 19:53 |
| mnaser | where do we draw the line if project maintainers in terms of maintainers not taking care of reviews (we use lack of release as a signal, can this be one?) | 19:54 |
| mnaser | mttr .. mean time to review :p | 19:54 |
| fungi | mnaser: to be clear, you're raising concern about the master branch change that the maintainers merged months ago, or the stable branch backports that the stable branch reviewers haven't looked at? | 20:23 |
| mnaser | fungi: just the fact that we're not getting traction on a simple backport | 20:24 |
| fungi | okay, so stable branch backports specifically | 20:24 |
| fungi | at least in this case anyway | 20:24 |
| fungi | keep in mind that the "maintainers" are not necessarily responsible for stable branches, though if there's nobody interested in reviewing stable branch changes then maybe that deliverable shouldn't have stable branches | 20:25 |
| fungi | in the past, stable branches were treated as a point of coordination for downstream distributors and consumers to collaborate on backports in common so they didn't duplicate one another's work | 20:27 |
| fungi | so this could also be a sign that ovn-bgp-agent needs a dedicated stable review group comprised of the people making and consuming those backports | 20:28 |
| fungi | anybody happen to know if next week's tc call is when the switch from zoom to jitsi is happening? just trying to make sure we know if the zoom room needs to be maintained for another week still | 21:36 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!