Archive for August 2009
Today everything went smoothly:
- Starting the day, Nagappan released LDTP 1.7, which comes with one my wanted features, uptime measures. Perfect to test Notify-OSD timings, i.e.
- Then I received an email from Debian LDTP maintainer, reminding me that we should be changing python-gnome2-desktop dependency, which is now deprecated.
- I packaged the new upstream version for Ubuntu and also changed the deprecated dependency.
- Then, the packaging training gang did an on-call review session, where you could talk directly to the sponsors and ask them to review your package. I attended and Colin Watson kindly reviewed my changes.
- I attached a new diff.gz to the bug report with the changes Colin had suggested.
- I went for lunch. By the time I came back the new LDTP package had been sponsored and uploaded to universe. Again, just in time before holidays and Karmic feature freeze.
Yes, if you updated your Karmic repositories lately, you can install Mago just typing “sudo apt-get install mago”. What does that mean? Not much, for the moment.
We have packaged the library and harness, but not the tests. Once you have installed Mago in your machine, you can start writing tests using the library, you will be able to run the tests with the Mago harness and get nice reports in XML and HTML. You won’t have the already written tests, though. Tests change a lot, so it does not make sense to keep them in the repositories, which are quite static. PPAs are a much better place for tests, which I am planning to maintain.
I still have a lot of work to be done regarding this: I have to set up the PPA for the tests and update the documentation at the Mago site, to start. Why did I push Mago into Karmic, then? There are two main reason: Feature Freeze and Holidays. Ubuntu development schedule has an important date called Feature Freeze, after which no new packages are generally accepted and only bug fixes are supposed to get uploaded. Karmic FF is happening August 27th, but I will be on holidays since August 14th, so it was now or never (or Karmic+1).
The main advantage of having Mago in the repositories is that, if a project wants to use it as part of the testing of their daily builds, they can set Mago as a Build-Depends of the project and forget about whether Mago is installed or not in the build machine. And, don’t worry, I will be updating the documentation and setting up the tests PPAs after my holidays, but, in the mean time, Mago is there, ready before Feature Freeze. Happy testing!