Thanks Sean, so ocata-eol[1] and pike-eol[2] patches were proposed for TripleO and they are merged, both ocata-eol and pike-eol tags got created after the patches merged. But still stable/ocata and stable/pike branches exist. Can someone from Release Team get them cleared so there is no option left to get cherry-pick proposed to these EOL branches. If any step from TripleO maintainers is needed please guide.
[1] https://review.opendev.org/#/c/677478/ [2] https://review.opendev.org/#/c/678154/
The release automation can only create branches, not remove them. That is something the infra team would need to do. I can't recall how this was handled in the past. Maybe someone from infra can shed some light on how EOL'ing stable branches should be handled for the no longer needed stable/* branches. Sean