Learn more about these different git repos.
Other Git URLs
As requested by @sgallagh, it wouid be nice to have RAWHIDEFTBFS and RAWHIDEFTI aliases that can be used by ELN to report bugs against "whatever release rawhide is now".
Example: 1868278 is the F34FTBFS tracker. It would also have the RAWHIDEFTBFS alias. On F34 branch day, 1868278 would keep the F34FTBFS alias but drop the RAWHIDEFTBFS alias. The newly created F35FTBFS bug would then get the RAWHIDEFTBFS alias.
(Repeat the above for the FTI tracker)
I have verified that Bugzilla will let us do this, so long as the alias is first removed from the old bug.
When do you need this? (YYYY/MM/DD) Tue 2021-02-09 (F34 branch day)
When is this no longer needed or useful? (YYYY/MM/DD) It will always be useful, but more useful if it's done before branch
If we cannot complete your request, what is the impact? ELN has to update their scripts every 6 months to point to a new tracker
Is this really useful? Rawhide is not a real "thing" from an infrastructure point of view, even in Koji. Adding additional random trackers that actually persist would be very annoying and add churn that doesn't necessarily make sense.
For example, if things actually change in Rawhide to silently resolve the breakage, how is this captured and resolved? Right now, that happens for free by virtue of us not filing a FTBFS/FTI bug for the next version.
Is this really useful?
I don't think Stephen would ask for it if it weren't.
Adding additional random trackers that actually persist would be very annoying and add churn that doesn't necessarily make sense.
That's not what this is. It's an alias so that the ELN tooling can file bugs against a stable bug alias instead of having to update the alias every branch day. Because ELN is built from rawhide, it doesn't branch. So without this change, current FTBFS are filed using the F34FTBFS tracker, but after the branch date, the tooling would have to update to use the F34FTBFS tracker.
This doesn't change the number of bugs that get filed, it just consolidates the effort into a single place. Releng is already creating new FTBFS trackers on branch day, so it makes sense to have them update the alias, too, instead of relying on consumers to make changes individually.
Metadata Update from @mohanboddu: - Issue tagged with: low-trouble, medium-gain, ops
Login to comment on this ticket.