launchpad development|
Size: 2503
Comment: Both exports and builds are now set. Updated the schedule accordingly
|
Size: 2574
Comment: Added status
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
= Status = <<Include(Translations/LanguagePackSchedule/Status)>> |
Purpose
This page documents the schedule of automatic translations tarball exports from Launchpad to be used as a source to langpack-o-matic to create the Ubuntu language packs.
Status
Distro Series |
Launchpad Exports |
Language Pack Builds |
Notes |
Quantal |
Enabled |
Enabled |
|
Precise |
Enabled |
Enabled |
|
Lucid |
Enabled |
Enabled |
|
Current export schedule (as of 2010-11-24)
Note: these are the starting days of the exports. The cron jobs to start generating the language-pack tarballs start on these days. Then langpack-o-matic picks them up the next day.
- Export starts: 22:00 UTC
- Build starts: 14:00 UTC next day
Weekday |
Launchpad Exports |
Language Pack Builds |
Notes |
Monday |
none |
- |
|
Tuesday |
Unusually long export times might hit Wednesday early rollouts |
||
Wednesday |
none |
Launchpad releases day |
|
Thursday |
none |
Ubuntu releases day |
|
Friday |
- |
||
Saturday |
none |
- |
|
Sunday |
none |
none |
- |
Notes
- We should avoid generating language packs on Wednesdays, which are Launchpad rollout days
- If language pack generation on Tuesdays take longer than usual (say 10h), we might even hit our early Wednesday rollouts and language packs might not be generated.
- The timing is chosen so we hit the times when we usually expect the lowest load. Most of the translation work happens in Europe, South America and Asia, and 22:00 UTC should mean less load on LP due to translation activity. With DB slaves, though, this is probably not something we should worry about.
Launchpad crontabs live in a branch on devpad:/code/pqm/crontabs/launchpad-production/ (look at the loganberry-launchpad file).
