Hi Bjoern, Thanks for inviting and coordinating everything ( sorry for the late reply, it was a busy week ) :) I'll try to join when it is possible, though the time could be a bit late in China. An obstacle is I am not sure if it is possible to make a call successfully from home ( I don't have a tie line at home ), will that be an SIP call or something else?
> prototype agenda for the first call: > structured manual testing: > - oneshot populating Ubuntu checkbox for LibreOffice 3.5? (Nicholas Skaggs) > - syncing checkbox from litmus for LibreOffice 3.6 (Yifan Jiang) Yes, I think it would be great if we can sync the stuff automatically. I prefer to maintain test cases in Litmus since it has a libreoffice project specific structure and maintainable already. Also from the testing statistics people is starting to get familiar with it: https://tcm.documentfoundation.org/ As for the test cases content, we actually improve the testing from time to time, but unfortunately I myself do not usually have sufficient time to do everything I wanted. It would be great if we have extra QAs to write the test cases, which is also one of the most important aspect we encourage people to do in Litmus: http://wiki.documentfoundation.org/QA/Testing/Test_Case http://wiki.documentfoundation.org/Litmus/Litmus_User_Guide#Populate_New_Test_Cases Meanwhile the good thing is we have a growing number of people who is running testing, and it would be fabulous if more people from Ubuntu community could help this out :) Best wihses, Yifan On Wed, Mar 07, 2012 at 02:45:13AM +0100, Bjoern Michaelsen wrote: > Hi all, > > > I hope to repeat this call biweekly to discuss and coordinate ongoing QA > issues, it would be great to have QA-contributors for the topics below able to > join this call. > > upstream bugwrangling: > - >1000 NEEDINFO bugs, what can we do about it? (Rainer Bielefeld, Cor Nouws) > - general bug stats (Rainer Bielefeld) > - submarine bugs (aka important bugs that stay undiscovered too long) (Cor > Nouws) > distro bugwrangling: > - upstreaming criteria/customs > (Christopher M. Penalver, Petr Mladek, Caolan NcNamara, Rene Engelhard, > Jan Holesovsky) > community testing, communication: > - how do we recruit more QA-interested contributors? (Cor Nouws, Sophie > Gaultier) > - can we have QA-related EasyHacks? Can we explicitly promote those? (all) > regression testing/bibisect: > - how do we broaden the bibisect know-how (Korrawit Pruegsanusak, Bjoern > Michaelsen) > - currently 27/27 bibisected bugs are older than the bibisect-range: > - do we maybe need a bibisect for 3.4? > - might indicate trouble during the bigmerge > - bibisect bugzilla etiquette > unittests/automated testing: (Markus Mohrhard) > - overview of what we have > - can we get non-developers into this, is there a way for non-C++ coders to > get involved? > > Although I know not everyone proposed might be able to join the call, I would > be happy if you try. If there are additional issues needing to be discussed, > please reply to this mail with your addition. I will post the phone conference > numbers later. > > Best, > > Bjoern > _______________________________________________ > List Name: Libreoffice-qa mailing list > Mail address: [email protected] > Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa > Problems? > http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://lists.freedesktop.org/archives/libreoffice-qa/ > _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: [email protected] Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
