ubuntu-translations-coordinators team mailing list archive

[David Planella <david.planella@xxxxxxxxxx>]

El dt 23 de 11 de 2010 a les 21:34 +0100, en/na Martin Pitt va escriure:
> Hello David,
> 
> sorry for the delay. It took me a while to find some time to repair
> the automatic langpack building from cron (it was mysteriously
> crashing from cron, but worked manually). It's (hopefully) working
> again now.
> 

Hi Martin,

Great to hear that, thanks!

> David Planella [2010-11-15 15:41 +0100]:
> > In theory, the next Lucid delta language pack should get all those new
> > translations, but the truth is that the code that produces the export
> > does not know about message sharing, as Jeroen was pointing out, so it
> > does not consider the new software-center translations coming from
> > Maverick as "changed" and thus are not exported.
> 
> Ah, I see. This is not something I can easily fix on my side, though,
> AFAICS?
> 

No, it's a bug in Launchpad. After talking to Danilo, I ended up filing
https://bugs.launchpad.net/rosetta/+bug/675627 ("Delta language pack
exports are not message sharing aware").

> > They will only be exported in the next full export, which will get to
> > users in the next full language pack.
> 
> That's fine. We do them from time to time anyway, at latest right
> before the next LTS point release.
> 

Yeah, that's a good workaround for now.

> > Going back to the Maverick language packs, Henning was telling us in a
> > previous e-mail that the translations export cron job from Launchpad had
> > already been set according to the "Launchpad Exports" column in the
> > schedule [1].
> > 
> > Martin, in order for the schedule to be up to date do you think you
> > could update the build part according to the "Language Pack Build"
> > column?
> > 
> > This would mean:
> >       * Updating the days when builds happen according to the schedule
> 
> Done. I used the proposed days, from [1] i. e. the days in bold.
> 

Perfect, thanks.

I've now done the final update to the schedule at:

        https://dev.launchpad.net/Translations/LanguagePackSchedule

If you guys have got a few spare minutes, could you please have a quick
look at it for a final double-check?

> >       * Activating the Maverick PPA builds
> 
> Done. They should fire tomorrow afternoon (Europe time), I'll watch
> whether it actually works, and fix up as necessary.
> 

Ack.

> >       * Setting up the Natty builds, to be started on Alpha 1
> 
> Prepared, but not activated. I want to do the first build manually
> once we have an export.
> 

Also ack.

Notice that if you want to test this earlier, it seems we've got some
full exports already:

https://translations.launchpad.net/ubuntu/natty/+language-packs

In any case, I'm in touch with Kate to see if we can add a "Release
first language packs" milestone on Alpha-1 in the release schedule in
the future, so that we can keep track of this in the official calendar.

> >       * Activating the Lucid PPA builds
> 
> Done.
> 

Ack, thanks.

Also marked https://bugs.launchpad.net/langpack-o-matic/+bug/670241 as
fixed.

> >       * Dropping the Karmic PPA builds from the schedule
> 
> Dropped from my cronjobs.
> 

Great. Here's an idea, which I can't remember if I mentioned at the UDS
session. Do you guys think it might be worth releasing a final language
pack when distros are dropped from the schedule?

This way these old releases would benefit from all translations done
through message sharing as well.

Do you guys think it's a good idea? Is the additional effort vs. benefit
worth it?

Thanks.

Regards,
David.

-- 
David Planella
Ubuntu Translations Coordinator
www.ubuntu.com / www.davidplanella.wordpress.com
www.identi.ca/dplanella / www.twitter.com/dplanella

Attachment: signature.asc
Description: This is a digitally signed message part