Learn more about these different git repos.
Other Git URLs
I'd like to avoid the desktop background be a blocker bug by moving the deadline up a little bit in the release schedule. RIght now, the wallpaper package deadlines fall at about the beginning of the freezes. I'd like to move that up to be 2 weeks prior to freeze as a starting point.
Another option that @mattdm brought up is to have the next set of backgrounds ready at the branch point. So when, for example, Fedora 32 branches from Rawhide, the default backgrounds in Rawhide would change to be the Fedora 33 backgrounds. This way the background follows the release as it branches. Of course, this would require playing catch up, so if we go with this option, we might move the deadline a little bit up over the course of a few releases.
I'll leave it up to the Design team to figure out what is the most sensible way to avoid having desktop backgrounds be a blocker days before Go/No-Go.
If the deadline was moved 2 weeks prior to the Beta Freeze, it looks like it would fall on or about the same time as the release branches from Rawhide.
2019-08-13 Branch F31 from rawhide 2019-08-27 Beta Freeze
https://fedoraproject.org/wiki/Releases/31/Schedule https://fedoraproject.org/wiki/Releases/30/Schedule
Going by the F30 schedule, that would mean the backgrounds would need to be in place around February 14.
@dan1mal Yeah, that's right — but the idea is that we'd actually do the Fedora 33 backgrounds then — so, not just a little earlier in the release cycle, but far earlier at the start. (And we'd want an F32 background ASAP — the branch for that was a month ago already.)
Can it wait a release? Im on maternity leave until end of Jan, unless someone else can step up to manage the process for F32.
Yeah, i'm +1 for waiting a release before changing this.
So just to poke at this again :) my proposal would be:
2020-08-11 Fedora 33 2021-02-09 Fedora 34 2021-08-10 Fedora 35 2022-02-08 Fedora 36
... with maybe a plan each time to review the feedback during the beta phase and land any changes in the days before (ideally not the day of!) the final freeze.
@mattdm I think we are on track to meet this now, would you agree? Is this just a matter of @bcotton to update the schedule now that the team is on this track?
Metadata Update from @duffy: - Issue tagged with: triaged
I forget exactly what the details we discussed on this were, so I'm going to explicitly list changes and let someone tell me where I'm wrong. :-)
Using the Fedora Linux 35 Design schedule:
Basically, I'm leaving that last set of steps for you to tell me how you want it to look and I'll just plug the dates into the schedule-o-matic.
@duffy does the above work for you? Any edits for the last point?
Hi @bcotton I dont know abt the removed lines. It shoukd be 35 not 3y re bullet #3. The last set of steps, just drop. We basically just need one event to start the process and then can go by the rawhide branch and beta freeze dates, like a week or two before each (maybe 2 is better)
I would have the process start at like, the beta freeze of the prior release.
does that help?
@duffy
It shoukd be 35 not 3y re bullet #3.
Ah, right. I was going by what I remembered Matthew saying, not what he put in the comments above.
We basically just need one event to start the process and then can go by the rawhide branch and beta freeze dates, like a week or two before each (maybe 2 is better)
Okay, so the F35 wallpaper process would have started on 2021-02-23? I'll have to think about how to implement that, since the release schedules are basically self-contained. I guess it depends on the answer to this question: would you want "Start F35 wallpapers" to appear on the F34 schedule, the F35 schedule, or both?
LMK if it'd be easier for me to set up 15 minutes for me to share my screen with you, too.
@bcotton Yeh - the F35 process actually started in January 2021 and we'll be starting the F36 process soon. I don't know if that's the right timing or if we are still behind where we should be?
the F35 process actually started in January 2021 and we'll be starting the F36 process soon. I don't know if that's the right timing or if we are still behind where we should be?
Yeah, I think that's on track. The goal would be to have F36 done by branch day (2022-02-08)
Okay, that's doable. Would you want "Start F37 wallpaper process" to appear on the F36 schedule, the F37 schedule or both?
And you just want a "start the process" and "wallpaper deadline" tasks, right?
@duffy here's a version of the F36 design schedule with what I understand to be the changes we're making. If that looks right, I'll start doing the F37–42 schedules.
I've gone with the draft above. If you decide later to make changes, you can file an issue in the schedule repo
Metadata Update from @bcotton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.