Goal:

decide on a branching strategy for konflux-data: https://gitlab.com/redhat/rhel-ai/konflux-data

current state:

• for each repo for each branch there is a commit sha in the .tekton pipelines. renovate tries to keep things in shape, but it is out of control.

proposed state:

• use release branches for konflux-data
• use these release branches in .tekton pipelines in the matching release branches
• use main in the main branch of each repository

why?

• less things to renovate
• only keep konflux-data up-to-date
• possibly add a repository for pipelines testing purposes, that runs the release branch of konflux-data.

Acceptance Criteria:

• all repositories use main in the main branch
• renovate is set to automatically update from main to the release branch per repository (sort of an automated release step)

Open questions:

Any additional details, questions or decisions that need to be made/addressed

• <your text here>
• …