String Freeze milestone timing
Jan Kurik <[email protected]>
| Newsgroups | gmane.linux.redhat.internationalization |
|---|---|
| Message-ID | <CA+Sa5Fp1haopxbX5dhyKJJ8NKLD0GTv7+do9tneC=61hYArGGA@mail.gmail.com> |
Hi Translators, during discussion on the FLOCK it has been realized we have some issue with Software String Freeze milestone. The issue is caused mostly by changing some key milestones as a consequence of "No More Alphas" Change [1]. In the past the Software String Freeze milestone was tight together with Alpha Freeze. After we implemented the "No More Alphas" Change [1] and we moved Branching closer to Beta Freeze, we are now in the situation when we need to come up with some conclusion how to plan the Software String Freeze milestone. AFAIK there are two requirements this milestone should fulfil: * The milestone needs to be planned after Branching * There should be enough time for translators to do the job before Software Translation Deadline (which is currently planned two weeks before Beta Freeze) Having the Branching 3 weeks before Beta Freeze does not give enough room for translations (comparing to the state before implementation of "No More Alphas" Change [1]). What I see as a possibility now is to have the Software String Freeze milestone one week after Branching and move Software Translation Deadline to the same date as Beta Freeze. This gives us the maximum time period between the "Software String Freeze" and "Translation deadline" we can currently have (even it is just two weeks). What do you think ? Will such a timing works for these two milestones ( Software String Freeze & Software Translation Deadline ) ? Or anyone have a better proposal ? [1] https://fedoraproject.org/wiki/Changes/NoMoreAlpha Thanks for any feedback, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic _______________________________________________ trans mailing list -- [email protected] To unsubscribe send an email to [email protected]