| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-05-12 | |||
| 02:51:25 | openstackgerrit | likui proposed openstack/nova master: Replace getargspec with getfullargspec https://review.opendev.org/c/openstack/nova/+/790405 | |
| 02:51:25 | openstackgerrit | likui proposed openstack/nova master: Replace getargspec with getfullargspec https://review.opendev.org/c/openstack/nova/+/790405 | |
| 09:03:46 | openstackgerrit | Merged openstack/osc-placement master: Support auto-negotiated microversion https://review.opendev.org/c/openstack/osc-placement/+/696028 | |
| 09:03:46 | openstackgerrit | Merged openstack/osc-placement master: Support auto-negotiated microversion https://review.opendev.org/c/openstack/osc-placement/+/696028 | |
| 09:03:56 | openstackgerrit | Merged openstack/osc-placement master: Switch default to use latest microversion https://review.opendev.org/c/openstack/osc-placement/+/696040 | |
| 09:03:56 | openstackgerrit | Merged openstack/osc-placement master: Switch default to use latest microversion https://review.opendev.org/c/openstack/osc-placement/+/696040 | |
| 09:12:47 | gibi | \o/ that is a real usability improvement ^^ | |
| 09:12:47 | gibi | \o/ that is a real usability improvement ^^ | |
| 09:15:02 | kashyap | gibi: or anyone: Do you know if any other non-OpenStack project using 'reno' for release notes management? | |
| 09:15:02 | kashyap | gibi: or anyone: Do you know if any other non-OpenStack project using 'reno' for release notes management? | |
| 09:15:33 | stephenfin | I use it for my own stuff | |
| 09:15:33 | stephenfin | I use it for my own stuff | |
| 09:15:36 | gibi | kashyap: I'm not aware of any but I never searched for it | |
| 09:15:36 | gibi | kashyap: I'm not aware of any but I never searched for it | |
| 09:15:38 | kashyap | Or is it closely tied to how OpenStack produces docs? | |
| 09:15:38 | kashyap | Or is it closely tied to how OpenStack produces docs? | |
| 09:15:58 | kashyap | stephenfin: I see, good to know. It's not tied to OpenStack's docs tooling, right? | |
| 09:15:58 | kashyap | stephenfin: I see, good to know. It's not tied to OpenStack's docs tooling, right? | |
| 09:16:04 | stephenfin | It's not closely tied to how we produce docs, but it is closely tied to our branching model | |
| 09:16:04 | stephenfin | It's not closely tied to how we produce docs, but it is closely tied to our branching model | |
| 09:16:19 | kashyap | stephenfin: The reason I ask is, QEMU upstream uses MediaWiki for changelog. E.g. https://wiki.qemu.org/ChangeLog/6.0 | |
| 09:16:19 | kashyap | stephenfin: The reason I ask is, QEMU upstream uses MediaWiki for changelog. E.g. https://wiki.qemu.org/ChangeLog/6.0 | |
| 09:16:27 | kashyap | stephenfin: I'm wondering if I can bring them to start using 'reno' | |
| 09:16:27 | kashyap | stephenfin: I'm wondering if I can bring them to start using 'reno' | |
| 09:16:44 | kashyap | Or any other generic Git-based rel note management. | |
| 09:16:44 | kashyap | Or any other generic Git-based rel note management. | |
| 09:17:14 | stephenfin | For example, I tried to integrate it into Sphinx, but they have a merge-back model whereby you propose things to stable branches and then periodically merge those back into master. That breaks reno, which expects branches stable branches to diverge | |
| 09:17:14 | stephenfin | For example, I tried to integrate it into Sphinx, but they have a merge-back model whereby you propose things to stable branches and then periodically merge those back into master. That breaks reno, which expects branches stable branches to diverge | |
| 09:17:20 | stephenfin | kashyap: towncrier | |
| 09:17:20 | stephenfin | kashyap: towncrier | |
| 09:18:31 | kashyap | stephenfin: Oh, I see. So, if a project has non-converging stable -> master approach, then 'reno' is good? | |
| 09:18:31 | kashyap | stephenfin: Oh, I see. So, if a project has non-converging stable -> master approach, then 'reno' is good? | |
| 09:18:33 | stephenfin | kashyap: it's not as clever, but that's possibly a good thing. No git parsing logic. You simply create news fragment files and then once, before a release, you run a manual step to combine those into once NEWS/CHANGELOG/<whatever> file | |
| 09:18:33 | stephenfin | kashyap: it's not as clever, but that's possibly a good thing. No git parsing logic. You simply create news fragment files and then once, before a release, you run a manual step to combine those into once NEWS/CHANGELOG/<whatever> file | |
| 09:18:54 | kashyap | stephenfin: Didn't know of 'towncrier'; /me looks up. | |
| 09:18:54 | kashyap | stephenfin: Didn't know of 'towncrier'; /me looks up. | |
| 09:19:00 | stephenfin | kashyap: Yes, I think that's a fair summary | |
| 09:19:00 | stephenfin | kashyap: Yes, I think that's a fair summary | |
| 09:19:30 | kashyap | stephenfin: Okay; thanks for the suggestion. I'll check w/ the QEMU upstream folks to guage the appetite | |
| 09:19:30 | kashyap | stephenfin: Okay; thanks for the suggestion. I'll check w/ the QEMU upstream folks to guage the appetite | |
| 09:19:44 | kashyap | Since I got used to 'reno', I abhor MediaWiki :D | |
| 09:19:44 | kashyap | Since I got used to 'reno', I abhor MediaWiki :D | |
| 09:20:17 | stephenfin | though you also occasionally need to go in and create a static summary changelog (or whatever you want to call them), whereby you instruct reno not to scan past commit N and simply generate a static listing | |
| 09:20:17 | stephenfin | though you also occasionally need to go in and create a static summary changelog (or whatever you want to call them), whereby you instruct reno not to scan past commit N and simply generate a static listing | |
| 09:20:33 | stephenfin | if you don't do this, the build time will continue to grow with your commit history | |
| 09:20:33 | stephenfin | if you don't do this, the build time will continue to grow with your commit history | |
| 09:21:10 | kashyap | stephenfin: Ah, that's a very useful thing to know; thanks. | |
| 09:21:10 | kashyap | stephenfin: Ah, that's a very useful thing to know; thanks. | |
| 09:21:19 | stephenfin | compare e.g. releasenotes/source/newton.rst with releasenotes/source/ocata.rst | |
| 09:21:19 | stephenfin | compare e.g. releasenotes/source/newton.rst with releasenotes/source/ocata.rst | |
| 09:21:30 | stephenfin | the git log for the former should explain some of the rationale | |
| 09:21:30 | stephenfin | the git log for the former should explain some of the rationale | |
| 09:21:31 | kashyap | * kashyap goes to compare | |
| 09:21:41 | stephenfin | I should probably get this written down in the reno docs... | |
| 09:21:41 | stephenfin | I should probably get this written down in the reno docs... | |
| 09:21:58 | stephenfin | hope that helps | |
| 09:21:58 | stephenfin | hope that helps | |
| 09:22:31 | kashyap | stephenfin: Yes, very much. Please document the above useful bits you just said. It helps non-OpenStack projects to evaluate it clearly | |
| 09:22:31 | kashyap | stephenfin: Yes, very much. Please document the above useful bits you just said. It helps non-OpenStack projects to evaluate it clearly | |
| 09:23:06 | kashyap | Especially the non-converging branches expectation is a good one | |
| 09:23:06 | kashyap | Especially the non-converging branches expectation is a good one | |
| 09:29:08 | kashyap | I worry about the "occasionally don't forget to generate static summary" from dead branches -- it's easy to forget. /me thinks if there's a way to automate it (even if it's just an email reminder) | |
| 09:29:08 | kashyap | I worry about the "occasionally don't forget to generate static summary" from dead branches -- it's easy to forget. /me thinks if there's a way to automate it (even if it's just an email reminder) | |
| 09:33:39 | kashyap | stephenfin: Is Sphinx's merge-back model documented somewhere? | |
| 09:33:39 | kashyap | stephenfin: Is Sphinx's merge-back model documented somewhere? | |
| 09:33:56 | stephenfin | I don't think so | |
| 09:33:56 | stephenfin | I don't think so | |
| 09:34:43 | stephenfin | https://www.sphinx-doc.org/en/master/internals/contributing.html#bug-reports-and-feature-requests | |
| 09:34:43 | stephenfin | https://www.sphinx-doc.org/en/master/internals/contributing.html#bug-reports-and-feature-requests | |
| 09:35:13 | stephenfin | It's described in a round-about manner in the Getting started guide here | |
| 09:35:13 | stephenfin | It's described in a round-about manner in the Getting started guide here | |
| 09:35:27 | kashyap | Ah; thanks :) | |
| 09:35:28 | kashyap | Ah; thanks :) | |
| 10:05:37 | openstackgerrit | Balazs Gibizer proposed openstack/nova-specs master: Allow provider re-parenting in placement https://review.opendev.org/c/openstack/nova-specs/+/788243 | |
| 10:06:17 | sean-k-mooney | wait what | |
| 10:06:17 | sean-k-mooney | wait what | |
| 10:07:01 | sean-k-mooney | why makeing osc using max is a huge breaking change | |
| 10:07:01 | sean-k-mooney | why makeing osc using max is a huge breaking change | |
| 10:07:29 | gibi | sean-k-mooney: it is the CLI | |
| 10:07:29 | gibi | sean-k-mooney: it is the CLI | |
| 10:07:33 | sean-k-mooney | i hope that is going to be a major version bump | |
| 10:07:33 | sean-k-mooney | i hope that is going to be a major version bump | |
| 10:07:34 | gibi | use by humand | |
| 10:07:34 | gibi | use by humand | |
| 10:07:48 | sean-k-mooney | gibi: yes but it was intended to be stable for scripting | |
| 10:07:48 | sean-k-mooney | gibi: yes but it was intended to be stable for scripting | |
| 10:08:21 | gibi | if somebody scripts against the CLI instead of against the SDK then I'm a sad panda | |
| 10:08:21 | gibi | if somebody scripts against the CLI instead of against the SDK then I'm a sad panda | |
| 10:08:24 | sean-k-mooney | it predatae the sdk and not eveytone used python so saying use the sdk is not valid either | |
| 10:08:24 | sean-k-mooney | it predatae the sdk and not eveytone used python so saying use the sdk is not valid either | |
| 10:08:46 | sean-k-mooney | gibi: it was one of osc design goal to not do this | |
| 10:08:46 | sean-k-mooney | gibi: it was one of osc design goal to not do this | |
| 10:09:22 | sean-k-mooney | gibi: i would be fine with osc defaulting to the miniums micorverion required for the parmateres you passed | |
| 10:09:22 | sean-k-mooney | gibi: i would be fine with osc defaulting to the miniums micorverion required for the parmateres you passed | |
| 10:09:54 | sean-k-mooney | since that is still stable but follow the project client and going to latest is a regression in my view | |
| 10:09:54 | sean-k-mooney | since that is still stable but follow the project client and going to latest is a regression in my view | |
| 10:11:14 | gibi | OK, I will push a revert of the last patch that switch the default behaviopr | |
| 10:11:14 | gibi | OK, I will push a revert of the last patch that switch the default behaviopr | |
| 10:11:18 | gibi | stephenfin: ^^ | |
| 10:11:18 | gibi | stephenfin: ^^ | |