Thursday, 2021-11-04

*** gibi_pto_back_thu is now known as gibi07:56
pas-ha[m]hi all, I noticed that there's no stable/xena branch in openstack/tooz repo, while tooz is still listed as having tag "stable:follows-policy" in the governance repo https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml#L237810:21
pas-ha[m]did we miss to create branch / Xena release? or I missed something and tooz went to model w/o stable branches?10:22
pas-ha[m]tooz is also missing from list of Xena deliverables on https://releases.openstack.org/xena/10:24
*** lbragstad4 is now known as lbragstad10:33
*** lbragstad1 is now known as lbragstad10:43
opendevreviewStephen Finucane proposed openstack/debtcollector master: Remove six  https://review.opendev.org/c/openstack/debtcollector/+/81663810:45
opendevreviewStephen Finucane proposed openstack/debtcollector master: Remove unnecessary 'coding' lines  https://review.opendev.org/c/openstack/debtcollector/+/81663910:45
stephenfinhberaud: If you're about, that seems to be the final library still using six in oslo land. It would be nice to remove the dependency IMO ^10:46
hberaudstephenfin: ack10:53
hberaudstephenfin: please can you review this patch too https://review.opendev.org/c/openstack/oslo.context/+/81238810:53
hberaudussuri EM is coming10:54
opendevreviewHervé Beraud proposed openstack/oslo.policy stable/wallaby: Dropping lower constraints testing  https://review.opendev.org/c/openstack/oslo.policy/+/81664311:06
opendevreviewHervé Beraud proposed openstack/oslo.policy stable/victoria: Dropping lower constraints testing  https://review.opendev.org/c/openstack/oslo.policy/+/81664411:07
*** lbragstad7 is now known as lbragstad11:07
opendevreviewHervé Beraud proposed openstack/oslo.policy stable/ussuri: Map system_scope in creds dictionary  https://review.opendev.org/c/openstack/oslo.policy/+/81177011:08
opendevreviewHervé Beraud proposed openstack/oslo.policy stable/ussuri: Dropping lower constraints testing  https://review.opendev.org/c/openstack/oslo.policy/+/81664511:08
pas-ha[m]I have also noticed even more oslo projects that lack both stable/wallaby and stable/xena branches while being listed in the governance repo as following stable:follows-policy which implies there should be stable branches11:10
pas-ha[m]debtcollector futurist oslo.concurrency oslo.i18n oslo.log oslo.reports oslo.rootwrap (that one is probably deprecated in favor of privsep?) taskflow11:10
pas-ha[m]and they also are missing from releases.openstack.org list of deliverables for Wallaby and Xena.11:13
pas-ha[m]were those omitted by mistake? or the release model for those actually changed?11:13
pas-ha[m]hberaud: sorry to bother you but may be you could answer that ^11:15
hberaudpas-ha[m]: those projects moved to independent release model several months ago http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018527.html11:18
hberaudand the independent release model doesn't follow the coordinated series, so, no stable branches are created for those projects11:18
hberaudpas-ha[m]: by moving to the indepdent model our goal was to reduce our workload, by limiting the number of stable branches to maintain with limited contributors11:20
pas-ha[m]ok, I see, thanks. then the governance repo was not updated it seems :-/ still, it is weird that the versions corresponding to the releases / known to work with them are not listed on releases page...11:20
hberaudpas-ha[m]: why do you expect to see the governance repo updated? releases models are managed by the release team11:21
hberaudthe release page only list coordinated deliverables11:22
hberaudindependent deliverables aren't coordinated11:23
pas-ha[m]yes, but the project is listed in the governance repo as having particular tag that implies having stable branches. shouldn't that tag be removed from those projects if they no longer follow?11:24
pas-ha[m]https://governance.openstack.org/tc/reference/tags/stable_follows-policy.html#tag-stable-follows-policy11:34
stephenfinhberaud: done11:38
pas-ha[m]hberaud: that's exactly our case - we'd like to understand if there's any stable branch we can base our downstream on, or should we just stick to what's in the upper-constraints for a given release and cut the downstream branches from there... current situation is a bit confusing.11:39
pas-ha[m]also, in the past I already found some projects where stable branches were omitted by mistake :-) so I thought I should clear this out with oslo maintainers first.11:39
hberaudpas-ha[m]: Ah I see (the governance page point). I'll try to see if I can propose a patch to update this page.11:40
hberaudpas-ha[m]: you should stick to the upper-constraints for a given release11:40
pas-ha[m]yep, that's clear now, thanks11:41
hberaudstephenfin: thx11:41
hberaudpas-ha[m]: you are welcome11:41
opendevreviewMerged openstack/oslo.context stable/ussuri: Dropping lower constraints testing  https://review.opendev.org/c/openstack/oslo.context/+/81593413:01
opendevreviewMerged openstack/oslo.context stable/ussuri: Fix context from_dict() for system_scope  https://review.opendev.org/c/openstack/oslo.context/+/81238813:01
opendevreviewHervé Beraud proposed openstack/oslo.utils master: Remove deprecated timeutils functions  https://review.opendev.org/c/openstack/oslo.utils/+/81670013:50
opendevreviewHervé Beraud proposed openstack/oslo.utils master: Remove deprecated timeutils functions  https://review.opendev.org/c/openstack/oslo.utils/+/81670013:57
opendevreviewHervé Beraud proposed openstack/oslo.utils master: Remove deprecated timeutils functions  https://review.opendev.org/c/openstack/oslo.utils/+/81670014:01
opendevreviewHervé Beraud proposed openstack/oslo.utils master: Remove deprecated timeutils functions  https://review.opendev.org/c/openstack/oslo.utils/+/81670014:05

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!