Learn more about these different git repos.
Other Git URLs
Describe the issue We're planning to update to LLVM-14 in F36, and we would like to have a llvm-14 branch created for each package we are updating so that we can build pre-releases into side tags without disrupting development in rawhide. I wasn't aware of this being done before, so I wanted to know if this was allowed and if not what other options we might have.
The list of packages that would need the llvm-14 branch is here: https://fedoraproject.org/wiki/Changes/LLVM-14#Release_Notes
When do you need this? (YYYY/MM/DD) We need to know if creating the branches is allowed by 2021-12-15, so we have time to update the change proposal if we need to do something else. Otherwise, we don't need the branches until 2021-01-15
When is this no longer needed or useful? (YYYY/MM/DD) 2021-01-15
If we cannot complete your request, what is the impact? We would need to find an alternative way to build and test LLVM pre-releases.
I think you don't need privileged branches in dist-git and koji side-tags. I believe you can achieve the same result with private branches and building in COPR from them.
Metadata Update from @mohanboddu: - Issue tagged with: changes, f36
@sharkcz We could use COPR, but the disadvantages of this are no CI tests and also it takes a very long time to do builds on the emulated arches. If there is a way we could do this in Koji, that would be our preference.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.