[Bug 1435423] New: Need to fix wallpaper / background packaging situation

https://bugzilla.redhat.com/show_bug.cgi?id=1435423 Bug ID: 1435423 Summary: Need to fix wallpaper / background packaging situation Product: Fedora Version: rawhide Component: f26-backgrounds Severity: high Assignee: luya_tfz(a)thefinalzone.net Reporter: duffy(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: design-devel(a)lists.fedoraproject.org, luya_tfz(a)thefinalzone.net Description of problem: The packaging bits for providing the default desktop background are overcomplicated and cause issues every release. On top of that, there is a new source package every release, so every release we need to do a new package review. Once the new package is in, we have to adjust stuff in comps/spin-kickstarts. Just using one package with subpackages could save a lot of pain. There is legitimate complexity here, but someone should sit down and think about how this works and come up with a better approach - it should be possible but it's never on anybody's priority list until we get into another situation with wallpapers blocking the release. Going to no alphas in favor of rawhide serving as alpha, we need to change how it works anyway. Roshi offered to write a script to autogenerate a placeholder wallpaper that could be used until draft artwork was ready. Idea from today's F26 alpha go/no-go meeting: 1) After branch you make that have the current release stuff and move the previous one to desktop-backgrounds-f25 subpackage 2) maybe just one source package is OK, it'd have a lot of subpackages but you could just keep them around for as long as you want and the subpackages should have virtual provides 3) when we get to final, we push it to N+1 and at that point it never is an issue again Another idea: 1) the real problem we have here is a) there's far too much unnecessary work to do each cycle to actually meet the requirements and b) no-one seems to have taken responsibility for making sure all that work gets done every cycle, even though it's completely predictable and plannable-for and it should be someone's job as soon as possible after branching to put in the 'real' wallpaper for the release 2) the placeholder wallpaper should just always be in rawhide 3) when we branch the package is updated to the new one 4) the neat thing about doing it that way is that as long as the real wallpaper gets in *some time* before release, we're good, because then all pre-release builds would kinda 'automatically' have different wallpaper from all final releases 5) the placeholder wallpaper can always stay the same or just be changed when someone gets bored of it. it doesn't really matter so long as it's never the same as any final release wallpaper Nirik has volunteered to look into this. CCing adamw, sgallagh, and nb based on their participation / interest. -- You are receiving this mail because: You are on the CC list for the bug.