ExportsSchedule

Differences between revisions 1 and 6 (spanning 5 versions)
Revision 1 as of 2009-11-10 07:35:56
Size: 2741
Editor: 212
Comment: First version
Revision 6 as of 2010-02-15 13:22:03
Size: 2741
Editor: 88
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
= Exports schedule = = Translations exports schedule =
Line 9: Line 9:
 * Current [[https://dev.launchpad.net/Translations/LanguagePackSchedule|exports schedule]]:
  * Monday: [[https://translations.launchpad.net/ubuntu/jaunty/+language-packs|Jaunty]]
  * Wednesday: [[https://translations.launchpad.net/ubuntu/karmic/+language-packs|Karmic]]
  * Thursday: [[https://translations.launchpad.net/ubuntu/hardy/+language-packs|Hardy]]
  * Friday: [[https://translations.launchpad.net/ubuntu/intrepid/+language-packs|Intrepid]]
  * Saturday: [[https://translations.launchpad.net/ubuntu/karmic/+language-packs|Karmic]]
Translations from Launchpad are automatically exported on a regular basis as a tarball containing PO files for all languages. This tarball is then used by langpack-o-matic as the source to create the language pack packages.
Line 16: Line 11:
 * Proposed exports schedule:
  * Monday: [[https://translations.launchpad.net/ubuntu/jaunty/+language-packs|Jaunty]]
  * '''Wednesday: [[https://translations.launchpad.net/ubuntu/lucid/+language-packs|Lucid]]'''
  * Thursday: [[https://translations.launchpad.net/ubuntu/hardy/+language-packs|Hardy]]
  * '''Friday: [[https://translations.launchpad.net/ubuntu/karmic/+language-packs|Karmic]]'''
  * '''Saturday: [[https://translations.launchpad.net/ubuntu/lucid/+language-packs|Lucid]]'''

 * Proposals:
  * Drop Intrepid
  * Drop Hardy and produce the language packs on request (we should define a procedure)
 * [[https://dev.launchpad.net/Translations/LanguagePackSchedule|Current exports schedule]]
Line 29: Line 15:
From the u-t-c mailing list discussion, everyone seems to agree to drop Intrepid, so I believe we can do it straight away. I personally am not too sure about dropping Hardy, but I'd be fine with it if we define and document a clear procedure to request language pack updates. -- [[LaunchpadHome:dpm]] <<DateTime(2009-11-10T08:35:56+0100)>> From the u-t-c mailing list discussion, everyone seems to agree to drop Intrepid, so I believe we can do it straight away. I personally am not too sure about dropping Hardy, but I'd be fine with it if we define and document a clear procedure to request language pack updates. -- [[LaunchpadHome:dpm]] <<DateTime(2009-11-10T08:47:03+0100)>>
Line 35: Line 21:
  * Karmic PPAs seem to be disabled    * From UDS discussions, it seems that we still want weekly Jaunty PPA uploads -- [[LaunchpadHome:dpm]] <<DateTime(2009-12-10T16:30:36Z)>>
Line 43: Line 29:
We should probably discuss all this at UDS, but please, add your comments here. I'd still leave the Jaunty PPAs as they are, but perhaps reducing the frequency of uploads to monthly. In any case, we should update the text on the [[https://launchpad.net/~ubuntu-langpack/+archive/ppa|PPA page]] to reflect the current situation, since the current text is misleading. -- [[LaunchpadHome:dpm]] <<DateTime(2009-11-10T08:35:56+0100)>> === David ===
We should probably discuss all this at UDS, but please, add your comments here. I'd still leave the Jaunty PPAs as they are, but perhaps reducing the frequency of uploads to monthly. In any case, we should update the text on the [[https://launchpad.net/~ubuntu-langpack/+archive/ppa|PPA page]] to reflect the current situation, since the current text is misleading. -- [[LaunchpadHome:dpm]] <<DateTime(2009-11-10T08:47:03+0100)>>

=== Adi ===
Having the language pack PPA updated twice per weeks is very useful for both translators and developers.

PPA updates for latest stable release and current development release is a must.
Since we have message sharing between series it would make sense to also update the series linked with the latest stable or development release.

Now for moving those packages from PPA to ubuntu-updates I think this should be done on demand for all stable releases and only if they fix some bugs or a major number of translations were updated.
It is not of much use to update all languages each month since for 90% of them no significant strings were changes.
Maybe we can use the same process as for SRUs.

Introduction

The purpose of this page is to help on the planning of language pack exports and updates

Translations exports schedule

Translations from Launchpad are automatically exported on a regular basis as a tarball containing PO files for all languages. This tarball is then used by langpack-o-matic as the source to create the language pack packages.

Discussion

From the u-t-c mailing list discussion, everyone seems to agree to drop Intrepid, so I believe we can do it straight away. I personally am not too sure about dropping Hardy, but I'd be fine with it if we define and document a clear procedure to request language pack updates. -- dpm 2009-11-10 07:47:03

Language packs

  • Automatic PPA uploads
    • Do we still want weekly PPA uploads for Jaunty, or once per month? Or stop them and generate them on request?
      • From UDS discussions, it seems that we still want weekly Jaunty PPA uploads -- dpm 2009-12-10 16:30:36

  • Language pack updates
    • What do we do for Jaunty? It will probably depend on what we decide for the PPAs. Do we want montly updates?
    • We should define a schedule for Karmic. Proposal: monthly updates, 2 weeks after the PPA upload being tested. E.g. announce a 16th Nov PPA for testing and release the first language pack on the 30th Nov.

Discussion

David

We should probably discuss all this at UDS, but please, add your comments here. I'd still leave the Jaunty PPAs as they are, but perhaps reducing the frequency of uploads to monthly. In any case, we should update the text on the PPA page to reflect the current situation, since the current text is misleading. -- dpm 2009-11-10 07:47:03

Adi

Having the language pack PPA updated twice per weeks is very useful for both translators and developers.

PPA updates for latest stable release and current development release is a must. Since we have message sharing between series it would make sense to also update the series linked with the latest stable or development release.

Now for moving those packages from PPA to ubuntu-updates I think this should be done on demand for all stable releases and only if they fix some bugs or a major number of translations were updated. It is not of much use to update all languages each month since for 90% of them no significant strings were changes. Maybe we can use the same process as for SRUs.


CategoryTranslations

UbuntuTranslationsCoordinators/OngoingProjects/ExportsSchedule (last edited 2010-02-15 13:22:03 by 88)