| crohmann | Hey there everyone! I was wondering if this was the channel to reach maintainers of Designate. I ran into a bug and filed it at https://bugs.launchpad.net/ubuntu/+source/designate/+bug/1940976. But looking at the long list of unsolved bugs and issues I am now wondering if this was the right approach? | 13:42 |
|---|---|---|
| crohmann | nicolasbock: I also took the liberty to add you as substriber as you appear to already have implemented a fix with your patchset https://review.opendev.org/c/openstack/designate/+/776173 | 13:45 |
| nicolasbock | Hi crohmann . Yes filing a bug for this issue was the right approach. I'll try to have a look at this again soon. | 15:12 |
| frickler | crohmann: also, yes, this is the right channel, but also we are indeed rather low on contributors, so your help is very welcome. | 15:54 |
| frickler | there is a reason that we were listed on https://governance.openstack.org/tc/reference/upstream-investment-opportunities/index.html for some years, and the reason that we disappeared is not that the situation has significantly improved | 15:54 |
| nicolasbock | johnsom, frickler, eandersson: Could we cut a point release for Stein and Train? In particular I am looking at https://review.opendev.org/c/openstack/designate/+/744796 and https://review.opendev.org/c/openstack/designate/+/743611 which haven't been release but would be a nice to have in an actual release :) | 16:08 |
| johnsom | Yes, I can work on that today | 16:09 |
| nicolasbock | Thanks! | 16:13 |
| nicolasbock | How does that work for stein for example? | 16:13 |
| nicolasbock | Would we need to move the `stein-em` tag? | 16:13 |
| nicolasbock | johnsom: Something like https://review.opendev.org/c/openstack/releases/+/806020 ? | 16:16 |
| johnsom | hmm, extended maintenance is interesting, let me see. We may not be able to cut a release for that | 16:16 |
| johnsom | Ah, yeah, since those are both EM, no more releases. https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases | 16:18 |
| nicolasbock | I just found https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance | 16:19 |
| nicolasbock | But yes, you are right | 16:19 |
| nicolasbock | Interesting policy :) | 16:19 |
| nicolasbock | How is a customer supposed to get patches on top of an EM branch? | 16:19 |
| nicolasbock | I'll abandon my review in `releases` | 16:20 |
| johnsom | You can still merge patches in EM and pull from git, it just won't release as a tar ball, etc. | 16:21 |
| nicolasbock | Ok | 16:21 |
| nicolasbock | Thanks johnsom ! | 16:21 |
| johnsom | Really this all comes down to having resources to maintain six branches back, which becomes harder and harder over time. | 16:22 |
| nicolasbock | Yes that's true | 16:23 |
| crohmann | nicolasbock: frickler: Thanks a bunch for your kind responses - I am not trying to (just) push "my issues", but was wondering that having such a large list of (old) bugs makes it hard to see if an issue was known or if there is ongoing the development. I know those stale bots i.e. on GitHub are a pain and no gain for on some projects issue list, but they require people to keep adding and analyzing | 20:32 |
| crohmann | to a bug. And if you don't mind me asking: What ever happens to all those bugs that are not actively pursued by the OP or contributed to in any way, especially if the release is EoL? | 20:32 |
| crohmann | Neutron or Cinder do have those bug deputies and do write a little summary to the ML. But I am not trying to sound smart - if you lack the heads to analyze and tackle all those bugs there is no way a simple process or new role does change that. | 20:35 |
| nicolasbock | I completely agree with you with all of the issues and suggestions you raise here. It would be very helpful if we groomed outstanding bugs and issues and kept the information on them up to date. However, the main impediment we are facing as a project is a shortage of manpower not really one of procedure. | 21:06 |
| nicolasbock | crohmann, as frickler pointed out we have been afflicted with a shortness of contributors for a while. We welcome any help :) | 21:08 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!