The approach the current criteria were intended to back was one where
we would have something like rawhide-backgrounds or development-
backgrounds which contained a background image that was very obviously
a WORK IN PROGRESS kind of thing - picture of Beefy with "PRE RELEASE"
written on it, or something like that - and this would be the
*permanent* default background for Rawhide. 'Final' backgrounds would
then be introduced for each release after it branched from Rawhide.
This would have the happy side effect that if we didn't get around to
doing anything by the Beta release, the Beta release would come out
with the 'development' background, which we figured would be OK for a
Beta, rather than with the same background as the previous release,
which isn't.

Aside from that one, the other advantage of this approach is that it
means you only have to do work in each release branch, you don't also
have to keep changing things in Rawhide.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org