Fedora 27, due out October 2017, will not have an Alpha release. We're
adjusting the schedule around that, and there are some questions as to
where the put the translations deadlines. Traditionally, String Freeze
is defined as "Same day as Alpha Freeze", so obviously that's no longer
useful.
Take a look at the schedule as it stands now:
https://fedoraproject.org/wiki/Releases/27/Schedule
Right now, we the string freeze about a month before the beta freeze
(basically, in the same timeframe). This, however, includes putting the
string freeze before Bodhi Activation (which also used to happen at
Alpha) and even before the branch from Rawhide. This seems less than
ideal.
On the other hand, the Translation Deadline is usually a bit before the
Beta freeze. If we keep that _and_ move the String Freeze up to the
branch, that leaves only a week to do translations. If we move the
String Freeze up to the Bodhi Activation point, that puts it *after*
the Translation Deadline, which obviously makes no sense.
In this new model, were *should* these deadlines fit? Is it reasonable
to put the Software String Freeze the day of the branch (2017-08-16)
and the Translation Deadline at the Beta Freeze (2017-09-05), or is
that too late? What about putting the Software String Freeze at branch,
and Translation Deadline just two weeks later at Bodhi Activation
(2017-08-29)?
Thanks!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader