[tc][release] Removing TC tags framework - next steps for release notes
radoslaw.piliszek at gmail.com
Tue Feb 15 08:07:01 UTC 2022
Thanks, Előd, for starting this!
I have replied on the change - for the tags framework removal to
succeed without breaking the scripts we also need to remove other
references to tags.
The banner was the most obvious usage but the tags are still used for
(likely even less used/useful) other purposes.
On Mon, 14 Feb 2022 at 12:40, Előd Illés <elod.illes at est.tech> wrote:
> As far as I know the 'follows-stable-policy' tag is now works as kind of
> a reminder for release management team that the given deliverables needs
> some extra attention that it does not violate the stable policy. Though
> for example I always try to review the release content in this respect.
> For me this was a good indicator, but on the other hand, maybe it is not
> that relevant for the release team nowadays. If the TC decided that tags
> will be removed, I'm not against it. So I think it's OK to drop it.
> Regarding what needs to be done in release repository: I proposed a
> simple clean up script . I think there is nothing else to do.
> @Release Management Team: let me know if you see something else that i
> might missed.
>  https://review.opendev.org/c/openstack/releases/+/829014
> (irc: elodilles @ #openstack-release)
> On 2022. 02. 13. 21:14, Radosław Piliszek wrote:
> > Hello Release Team,
> > As you might have heard, the TC is removing the TC tags framework. 
> > The first step has already been proposed and is being voted on. 
> > The removal of certain parts seems to be affecting the release team
> > tooling, especially with the usage of the stable:follows-policy tag to
> > show a relevant banner. 
> > The proposed change purposely avoids breaking the releases repo and
> > awaits a "part 2" which cleans up everything
> > TC-tags-framework-related.
> > Thus, I am asking for your help to remove this dependency on the tags framework.
> > I understand there might be several approaches to this and need your
> > assistance to continue.
> > The simplest approach is to drop the relevant code - assuming it is
> > not actively used for release process purposes.
> > Obviously, for anything else I need your input on what the options are.
> > It is also possible that you would prefer to port this tag to your
> > internal metadata.
> > I am open to ideas and will help enact the changes.
> >  http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025554.html
> >  https://review.opendev.org/c/openstack/governance/+/822900
> >  https://opendev.org/openstack/releases/src/commit/768a12e233c23999db18c807c228b6ec0b042eea/openstack_releases/cmds/list_changes.py#L303
> > Kind regards,
> > -yoctozepto
More information about the openstack-discuss