problems with upgrade of kde

Richard JOHNSON nixternal at
Thu May 21 00:00:19 BST 2009

On Wed, May 20, 2009 at 06:57:17PM +0200, Harald Sitter wrote:
> Neversfelde was kind enough to provide us server capacity. Soon (i.e. as soon 
> as I am able to master up the code for that) we will direct all Ninja Release 
> Packaging through said server which should speed up the review process (since 
> the whole coordinator dude position gets eliminated so that any core-dev can 
> review the changes and upload at will) as well as help us do automated QA. 
> Because really, the fact that I spent at least one day for every release on 
> basic regression testing (e.g. file clashes) is simply ridiculous.

How is this automated QA to be completed? There is no AT-SPI support in
Qt/KDE yet.

> So in the future, file clashes should be detected by comparing the packages' 
> file lists. However, I'd like to note that with more resources we could do a 
> lot more (I am thinking real upgrade scenarios in chroots for example ;-)).

Will this be done by the pbuilder hooks I am assuming? Even these don't
catch them all of the time, because the docs packages did fine with the
pbuilder hooks, but after uploading, there were issues with the install
that pbuilder didn't catch. I still prefer manually doing some regression
testing, and think everyone in the entire community needs to do this as
well for packages they work on, if they don't already.

 Name|  Richard JOHNSON
Title|  Developer
Email|  nixternal at
GnuPG|  9554 2BCC 3AA2 3898 0939  56E7 3EC9 A39D 2E2C 0124
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : 

More information about the kubuntu-devel mailing list