as the 3.4.0 release is coming very soon I just opened Litmus again this
morning and was a bit shocked that there is more or less nothing in
Although there is some text about Litmus on
http://wiki.documentfoundation.org/QA nobody seems to use it yet.
So some questions,
a) who is testing the RCs? Some work seems still to be done in the wiki
,, although the amount of testers is pretty low.
b) what are we doing with Litmus? Weeks and months pass by and the whole
relase QA process looks like it is getting no momentum at all as opposed
to most of the other parts in the LO community.
My suggestion is bring Litmus to front. Even if it has some flaws and
tests for just some parts and languages of the product open and announce
it publicly and use it as the only tool to get content in it asap. If
people create an account and see that there is really work going on in
this tool they will stay and contribute more likely than at the moment.
I could live without an release QA process as described in the wiki,
dump Litmus and just work with the time based releases and blocker bugs
in bugzilla as the release criteria. But one way or the other there
needs to be some direction and decissions.
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/projects/
All messages sent to this list will be publicly archived and cannot be deleted
- [libreoffice-projects] status of release QA/Litmus · Michael Münch
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy