#1886 Draft Fedora 30 schedule
Closed 5 years ago Opened 5 years ago by mattdm.

I know this is early, but I think it helps everyone when we have consistent milestones we know well in advance. And the F28 schedule went so well that it seems like "hey, let's do that again!" is the right answer this time around.

So, this proposed schedule is exactly the F28 schedule, one year later (and adjusted to keep the Tuesdays):

https://fedoraproject.org/wiki/Releases/30/Schedule

What do you think?


I have no problems with the proposed schedule for turning the crank on another release, so +1.

I'm really starting to wonder if "hey, let's do that again" is the right thing for Fedora long-term though. However, that's a conversation for a different ticket.

I strongly agree that "hey, let's do that again" shouldn't be our default outlook in general. I think it's pretty good for the base release schedule, though.

Actually, I've been thinking about this a little bit. F28 is our first release with modularity, and I'm hoping that will be expanded for F29. I'd like to give that a little bit of time to find its groove. We took a full year for F21 after F20 to retool for the three editions strategy, and, actually, it seems like ten releases later, F31 might be a good time to do the same for the next steps in modularity. I don't want to do that just to be different, though — we should plan out what exactly we want to change. If we do have something significant we could accomplish with a different schedule, I'm open the idea of not waiting until F31.

This is all good topics for Flock. :)

Metadata Update from @bowlofeggs:
- Issue tagged with: meeting

5 years ago

This is on the agenda for Friday's FESCo meeting.

Metadata Update from @zbyszek:
- Issue untagged with: meeting
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata