If anyone is interested in helping out with writing and performing tests during this cycle, please answer this mail (and do read on).
---- We hardly do any testing at all during our cycle, currently. This needs to be changed. Naturally, we do required tests for our releases, the Beta releases and the final release, but other than that, there's no structured testing. There are two kinds of testing that we would like to do: * Quality Assurance Testing - to make sure there are no bugs for a wide range of applications * performance testing (which is rather a big topic) The most urgent type of testing we need to deal with is the first of those. (So far, what we have in testing documentation can be found here https://wiki.ubuntu.com/UbuntuStudio/TestingDocumentation) # QA testing I suggest we establish a plan for testing, write test cases, and such, until Debian Import Freeze (https://wiki.ubuntu.com/DebianImportFreeze), which is scheduled to happen Aug 7th this cycle. Debian Import Freeze is a great time to do testing on Debian imported packages, since those packages won't be changing before release. It also gives us some time to find bugs, report them and fix them (Testing can of course be done from day one of our development cycle. The more time we have to spot bugs and fix them, the better, but we should begin no later than Debian Import Freeze). So: * Test writing may starts any time * Testing of applications should begin no later than at Debian Import Freeze, Aug 7th Elfy has offered to give us a hand on this. If he likes, he could take the role of QA lead for Ubuntu Studio during the next cycle, and mentor us into set up testing. What do you think elfy? The people who write the tests should know the applications they write the tests for. The test should be as simple as possible, but still designed to spot as many typical problems as possible for that application. # Performance testing During this cycle, as we might be getting a new kernel into the repo, we need to at least test linux-rt to see if it is worth the trouble to maintain it. Also, it might not be a bad idea to test performance on different DEs. We need to figure out how to do those tests, so if anyone has any experience in this, please let us know. -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel