Make Extras-testing better/faster

Posted on 2010-01-19 07:20 UTC by Sascha Makela. Status: Under consideration, Categories: Programming,

It seems that Extras-testing is not currently working very efficiently. There are many applications in there that have been there for very long time. While proper testing of applications is necessary, it serves nobodies interests if takes too long. This especially problematic for updates of existing applications.

For example: Lets presume there is App X that has finally been promoted form Extras-testing to Extras. After a while, it is reported that it has an critical fault that affects not only the application but also the entire system. Sure enough, the developer notices that he had a typo in his code and quickly makes the fix. He then uploads it to Extras-devel. This time his fortunate, as it took less than an hour to appear there and he immediately promotes this to Extras-testing. This takes a bit longer, but in 5 hours, the update is finally in Extras-testing. 
However, now the real problem starts. This critical update can reside in Extras-testing for days, weeks of even months! Of course, the developer could always recommend for the end-users to temporally activate Extras-testing to receive this critical update, but that would hardly be a good solution.


Talk link

Solutions for this brainstorm


Solution #1: Differentiate an update from a new application

Posted on 2010-01-19 07:20 UTC by Sascha Makela.

An update should not go through all the testing process again. Instead, there should be clear change log that would indicate what has been fixed and/or added. Then the testing could concentrate on those changes. Furthermore, an update should not need as much Karma as a new application to pass.

Latest activities to brainstorm Make Extras-testing better/faster