CI and stable branches

Has there been any discussion yet how we will handle gst-ci when we fork off module branches for 1.16?

I think there should also be a 1.16 branch for gst-ci then, but others seemed to think everything should always use master if I understood them correctly. I'm just not sure this is viable - the 1.16 branch CI should still work when we're on 1.20 in master or 2.x.

Thoughts?

Todo ahead of 1.16 branch-off

• teach the manifest generator to be aware of stable branches !118 (merged)
  • handle case of MRs that target 1.16 (top priority)
  • handle case of branch pushed to personal repo without MR, figure out if it's on top of 1.16 (git merge-branch --is-ancestor?), otherwise use master like now
• rework taggign of docker images to account for long lived images and branches
• make it possible to respin stable docker images on demand - moved to #33 (closed)

Todo and Checklist when branching off 1.16

• create 1.16 branch for gst-ci repository
• change all .gitlab-ci.yml in the other repositories to point to the template from the 1.16 branch