Ticket #1178 (new general)
Fedora 21 scheduling strategy
|Reported by:||jreznik||Owned by:|
|Cc:||tflink, ausil, jdulaney, bochecha, crobinso||Blocked By:|
It's time to take a look on F21 schedule, we discussed it a bit today on #fedora-devel and we agreed to bring it to FESCo meeting. F21 is a bit complicated - there's an on going effort for the 3 products offering and also there was a call to delayed F21. But I have two concerns: one is that the output from WGs is expected in January, so pretty late to be part of even delayed F21 schedule, other is that we did not hear any real proposal why to delay F21 and what would be achieved in that period of time (except QA automation and a few generic todos I'd say).
One option would be to schedule F21 as standard release, normal or bit shorter again and based on the output from WGs, plan F22+ releases the new way. It gives us possibility to have Flock synced with it (it is already under discussion on flock-planning list) before 3-products are started.
Another options is - if we still want to have delayed F21, we can try to have a formal call for proposals to know what we would be able to achieve and for how long it makes sense to prolong the release, based on Changes process for example, I'm willing to help with running it.