The side tag f38-toolchain for Changes/PortingToModernC is still targeted at f38, not rawhide, but the work needs to happen in rawhide. Eventually, this will make f38-toolchain less useful because not all build dependencies will be satisfiable in f38-toolchain.
f38-toolchain
There are different ways to address:
f39-toolchain
replace it with rawhide-toolchain
rawhide-toolchain
When do you need this? (YYYY/MM/DD)
2023-02-17 (tentative, before rawhide diverges too much from f38)
N/A
One of the validation methods package maintainers have for Changes/PortingToModernC becomes unusable.
Lets go with 'f39-toolchain' ?
If it's going to be around many more cycles we can add it into our branching docs?
Did you need us to retag anything from the f38-toolchain? Or you want to handle that?
Also, can we remove the f38-toolchain target now? ie, do you plan to do any more builds there?
f39-toolchain is fine. I hope it's going to the last of such branches. I can tag over the redhat-rpm-config and gcc builds myself. f38-toolchain can be removed (I think).
Thanks!
I'll just remove the target (so koji doesn't do newrepos for it and nothing can be built in it). It's not any cost to keep the tag around after that.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks. The new build target does not have the .tc dist tag, but that doesn't really matter for my purposes after all.
.tc