launchpad development|
Size: 1836
Comment: Added some additional feedback from an e-mail from Danilo
|
← Revision 60 as of 2023-11-06 13:45:18 ⇥
Size: 3014
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| Crontabs live in a branch on `devpad:/code/pqm/crontabs/launchpad-production/` (look at the `loganberry-launchpad` file). | = Status = |
| Line 7: | Line 7: |
| = Caveats = | For the live status on the language pack builds, have a look [[http://macquarie.canonical.com/~langpack/crontab|here]] |
| Line 9: | Line 9: |
| * 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 2200 UTC should mean less load on LP due to translation activity. With DB slaves, though, this is probably not something we should worry about. |
= Current export schedule = |
| Line 13: | Line 11: |
| = Current export schedule (as of 2010-06-29) = | 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: '''10:30 UTC''' * Build starts: '''10:30 UTC''' next day |
| Line 15: | Line 15: |
| These are the ''starting'' days of the exports. The cron jobs to start generating the language-pack tarballs start on these days, at 22:00 server time. Then langpack-o-matic picks them up at 14:00 (server time) the next day. | || '''Weekday''' || '''Launchpad Exports''' || '''Language Pack Builds''' || '''Notes''' || || '''Monday''' || [[https://translations.launchpad.net/ubuntu/jammy/+language-packs|Jammy]] || [[https://launchpad.net/ubuntu/mantic/+source/language-pack-en/+changelog|Mantic]] || - || || '''Tuesday''' || [[https://translations.launchpad.net/ubuntu/focal/+language-packs|Focal]] || [[https://launchpad.net/ubuntu/jammy/+source/language-pack-en/+changelog|Jammy (archive)]] || - || || '''Wednesday''' || [[https://translations.launchpad.net/ubuntu/trusty/+language-packs|Trusty]] || [[https://launchpad.net/~ubuntu-langpack/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=focal|Focal (PPA)]] || || || '''Thursday''' || [[https://translations.launchpad.net/ubuntu/bionic/+language-packs|Bionic]] || || Ubuntu releases day || || '''Friday''' || [[https://translations.launchpad.net/ubuntu/mantic/+language-packs|Mantic]] || [[https://launchpad.net/~ubuntu-langpack/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=bionic|Bionic (PPA)]] || - || || '''Saturday''' || [[https://translations.launchpad.net/ubuntu/mantic/+language-packs|Noble]] || || - || || '''Sunday''' || [[https://translations.launchpad.net/ubuntu/xenial/+language-packs|Xenial]] || || - || |
| Line 17: | Line 24: |
| * '''Monday:''' [[https://translations.launchpad.net/ubuntu/lucid/+language-packs|Lucid]] * '''Tuesday:''' [[https://translations.launchpad.net/ubuntu/maverick/+language-packs|Maverick]] * '''Wednesday:''' none (Launchpad releases day) * '''Thursday''': none * '''Friday:''' [[https://translations.launchpad.net/ubuntu/karmic/+language-packs|Karmic]] * '''Saturday:''' [[https://translations.launchpad.net/ubuntu/maverick/+language-packs|Maverick]] * '''Sunday''': none |
= Notes = |
| Line 25: | Line 26: |
| ''Notes: Hardy exports on request - TBD'' = Current Ubuntu language pack build schedule = * Maverick: `"0 14 * * 3,7"` |
* Launchpad crontabs live in a branch at lp:lp-production-crontabs (look at the `loganberry.canonical.com-launchpad` file). If the crontab entries need changing, do the updates yourself in a branch and propose a merge. * The old timing (was 22:00 UTC) used to be 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. * The new timing (10:30 UTC) was chosen to be after the new fastnodowntime window at 10:00 - 10:05 UTC during which the database will shortly be unavailable. This would break the export run and has to be avoided ([[https://bugs.launchpad.net/launchpad/+bug/849829|bug 849829]]). * Currently full language exports take much longer than expected, approaching 24h ([[https://bugs.launchpad.net/launchpad/+bug/684664|bug 684664]]) |
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
For the live status on the language pack builds, have a look here
Current export schedule
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: 10:30 UTC
Build starts: 10:30 UTC next day
Weekday |
Launchpad Exports |
Language Pack Builds |
Notes |
Monday |
- |
||
Tuesday |
- |
||
Wednesday |
|
||
Thursday |
|
Ubuntu releases day |
|
Friday |
- |
||
Saturday |
|
- |
|
Sunday |
|
- |
Notes
Launchpad crontabs live in a branch at lp:lp-production-crontabs (look at the loganberry.canonical.com-launchpad file). If the crontab entries need changing, do the updates yourself in a branch and propose a merge.
- The old timing (was 22:00 UTC) used to be 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.
The new timing (10:30 UTC) was chosen to be after the new fastnodowntime window at 10:00 - 10:05 UTC during which the database will shortly be unavailable. This would break the export run and has to be avoided (bug 849829).
Currently full language exports take much longer than expected, approaching 24h (bug 684664)
