From Fedora Project Wiki

Line 19: Line 19:
* <span style="color: blue">date13 and date14</span> are the tasks for translators and to be modified under trans-task-schedule
* <span style="color: blue">date13 and date14</span> are the tasks for translators and to be modified under trans-task-schedule
* <span style="color: green">date15</span> is the task for developers and to be modified under devel-task-schedule
* <span style="color: green">date15</span> is the task for developers and to be modified under devel-task-schedule
* There are some more tasks to be modified under trans-task, devel-task and rel-eng task accordingly
* There are some more tasks to be modified under trans-task, devel-task and rel-eng task accordingly (TBA in this page)
{| border="1"
{| border="1"
|- style="color: white; background-color: #3074c2; font-weight: bold"  
|- style="color: white; background-color: #3074c2; font-weight: bold"  

Revision as of 06:38, 29 July 2015

Current software translation activities are all scheduled within Alpha phase. Besides active development occurs after Alpha. This often leads string freeze breaks. The breaks informed to us are translated but have to rely on translator's great flexibility. For silent breaks, simply not translated as no one notice.

In order to coordinate translators resource more manageable, and to achieve higher localization percentage for Final Release (GA), G11N would like to move all software translation related events after Beta Freeze date. Please notice that this moves 'Software String Freeze' same date of Beta Freeze, thus allows the developers to change/add/remove strings freely to the last minute without soliciting to translation team.

The impact to other teams

Devel – due to string freeze date change, no more rebuild translation in Alpha phase, but Launch phase. RelEng – no longer need to compose the image for l10n-qa, as Beta PA can be utilized instead.

Affected events

  • Software String Freeze
  • Software Translation
  • Software L10N QA Test
  • Software Translation Deadline
  • Software Rebuild all translated packages by maintainers

Example with F23 Key Milestones

  • date & event indicates existing events with dates to be moved
  • date & event indicates proposed new dates
  • date13 and date14 are the tasks for translators and to be modified under trans-task-schedule
  • date15 is the task for developers and to be modified under devel-task-schedule
  • There are some more tasks to be modified under trans-task, devel-task and rel-eng task accordingly (TBA in this page)
Date Event metrics
date01 Fedora 23 Release
date02 Change Checkpoint: Proposal submission deadline (System Wide Changes)
date03 Side Tag Builds Deadline
date04 Mass Rebuild
date05 Branch Fedora 23 from Rawhide (Rawhide becomes future F24)
date06 Alpha Freeze (*)
date06 Software String Freeze
date06 Change Checkpoint: Completion deadline (testable)
date06 Bodhi activation point
date07 Alpha Release
date08 Software Translation Deadline
date9 Beta Freeze (*)
date10 Software String Freeze date10 = date9 - 0 day
date11 Change Checkpoint: 100% Code Complete Deadline
date12 Beta Release
date13 Software L10N QA Test (date13 to date13+1week) date13 = date12 - 0 day
date14 Software Translation Deadline date14 = date12 + 8 days
date15 Software: Rebuild all translated packages (date15 to date15+1week) date15 = date12 + 8 days
date16 Final Freeze (*)
date17 Fedora 23 Final Release

Amendment Suggestion