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.
Yes, I would totally support this approach, because I find it the most logical one.
Alternatively, we could introduce the development version of the background in Rawhide, just when Beta is branched,
so that it would be clear that there is something new going on. Beta would keep the Rawhide version until Final.
Example:
Beta 32 => Wallpaper A and Rawhide 33 => Wallpaper B
Beta 33 => Wallpaper B and Rawhide 34 => Wallpaper C
Another possibility, which is probably very difficult for the graphic team, however interesting:
Rawhide: Early development version of the Wallpaper with the chosen motif - clearly visible that it has the draft quality
Beta: Development version of the Wallpaper with the same motif, but much more precisely worked out.
Final: Final version of Wallpaper with the same motif.
The status of the Wallpaper would reflect the quality stages of Fedora.
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@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
--
Lukáš Růžička
FEDORA QE, RHCE
Purkyňova 115
612 45 Brno - Královo Pole
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
