Are we slotting this in under the "Appropriately means that the relevant software mechanism(s) for any given deployment must choose the software to be installed, updated or removed in ways that are broadly in line with the user's intent and typical expectations" note of the Installing, removing and updating software basic criteria? Basically saying users won't expect updates from testing when updating a stable release?

FinalBlocker +1

FinalBlocker +1

@nielsenb no, this is precisely tied to two requirements in Final: "No notices or alerts about pre-release status may be shown as part of installation or critical path actions on release-blocking desktops" (a -1 or higher versioned fedora-release is required to prevent pre-release warning being shown on live images) and "A fedora-release package containing the correct names, information and repository configuration for a final Fedora release must be present on release-blocking images and the appropriately versioned generic-release package must be available in the release repository" (I keep meaning to reword that one, but these days it's fedora-repos that has the repository configuration, and the meaning is clear - we need to have updates-testing turned off for release).

I actually just went ahead and updated the second one a bit to make it clearer.

FinalBlocker +1

Release F37 is no longer tracked by BlockerBugs, closing this ticket.