Hello,

I was thinking that our tooling will fail with these deliverables addition and tagging but apparently that's not the case so I would suggest to follow the 1st solution (using the existing tools, such as creating a yaml file etc).

Le lun. 28 juin 2021 à 20:15, Jeremy Stanley <fungi@yuggoth.org> a écrit :

On 2021-06-28 20:03:48 +0200 (+0200), Előd Illés wrote:
[...]
> If we stick to the tagging + deletion, then the next question is how to
> achieve this. There are a couple of options:
>
> 1. use the existing tools: such as creating a yaml file under
> deliverables/$series/ and add the $series-eol tag for the given repositories
> (I understand that these are not 'real' deliverables, but does that cause
> any issue for us?)
> 2. implement some new mechanism, similar to option 1, but clearly indicate
> that the tagging does not create any deliverables
> 3. manual tagging + deletion
>
> I think the 1st option is the easiest and since we already have the whole
> process there, we can simply use the existing tool.
>
> So what do you think?
> - Is that OK to tag these open old stable branches with $series-eol tag and
> then delete them?

WFM

> - If yes, which option from the above list is acceptable, or what else can
> we do?

The first one.

[...]

My two cents, I think it's okay to tag those old branches and delete
them, and I support option 1 as it helps create a bit of a
breadcrumb trail for future reflection.

As for how they got overlooked, I expect you're right. In the past,
well before we had any real release automation and tracking,
projects asked the Infra team to delete their old branches, and
quite often did not provide a complete list.
--
Jeremy Stanley

Hervé Beraud

Senior Software Engineer at Red Hat

irc: hberaud

https://github.com/4383/

https://twitter.com/4383hberaud