Blueprints for tomorrow

[Martin Pitt]

Hello Pierre,

the session was moved from yesterday, to a slot today where I was
already booked, so let's try to handle this via email (or schedule a
hangout next week).

Pierre Slamich [2013-05-13 16:36 +0200]:
> 5. For the Language Pack, it's exactly the input that I was looking for.
> Although he will probably not be able to implement it, I'd be grateful if
> Martin could give us pointers (30 to 60 min) of what we need to do for
> fully automating the full rebuild and enabling tests.

The building of langpack updates is already mostly automated: for the
development release they are automatically uploaded straight into
Ubuntu twice a week, and for the most recent stables the packages land
in https://launchpad.net/~ubuntu-langpack/+archive/ppa, from where
they are (supposed to be) copied to stable-proposed for each testing
round; that hasn't actually happened for a while, though.  The only
thing that I do manually is a full -base rebuild, as that needs to be
coordinated with Launchpad.

All the scripts and cron jobs to build langpacks are in
lp:langpack-o-matic, and this is the user documentation:
http://bazaar.launchpad.net/~ubuntu-langpack/langpack-o-matic/main/view/head:/doc/operator-guide.txt

In terms of testing, that currently happens manually. We expect
testers to install the latest packages, then reboot, verify that the
desktop still starts and looks "correct", and that you can run some
critical pieces of software which would allow us to supply another
update with a fix. In particular, update-manager, update-notifier, and
software-center. This can be automated with autopilot up to some
degree, but that hasn't happened so far.

Did you have something specific in mind for "fully automating the full
rebuild and enabling tests"?

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)