NOTFORMERGE: [RTADPA BW Tests] Freeze the hlt2 configuration being used for the BW Tests
Not for Merge
Summary
@jonrob @rjhunter @mvesteri.
Following this discussion, !3643 (comment 8229220), effectively three options were proposed re: 'freeze'ing the BW
-
Simplest: Don't do anything, requires experts to take appropriate care to advertise any changes that can affect BW to line authors/ liaisons
-
'Freeze' by default: Merge !3643 (closed) into 2024-patches. Then have to actively request the 'unfreeze' MR in any ci-tests that change binds. This was the original proposal, it places the burden on experts who are changing binds and/or the coordinators/maintainer to be aware of the relevant unfreezing MR.
-
'Freeze' on command: Don't merge !3643 (closed), but request it actively in ci-tests Use !3643 (closed) in selection MRs. This places the burden on liaisons+shifter/coordinators/maintainers to remember the freezing MR when requesting ci-tests.
In RTA WP3 today it was decided to do 1) right now + maintain !3643 (closed) for the ability to maybe carry out 3) if it's decided as necessary. Liaisons were asked for comment, heard no strong preference for any but @rjhunter asked them to read this MR and if they have any opinions to let us know.
ToDo:
-
Sprucing : Decided to leave sprucing 'unfrozen'. -
Local test nothings broken -
ci-test with all the BW Tests -
Review + Discussion