Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

Hi all,

I'm writing here, not sure if it's the right place, if you see a better one, push me to it :) Also it's a long time work, so no emergency, it's a kind of letter to Santa Claus ;-)

I was thinking about the TCS we need and I would like to work on it during the Christmas time. Thinking a bit more about it, there is several areas where we need (at least I lack) some tools. Before writing the list on the wiki, may be we could exchange here about it and bring you thoughts too :-)

For QA, l10n, Documentation, Marketing teams, I would like to have a list of features/commit automatically generated, if possible with the BZ number when it exists. This list is a real basis of work for the teams. I don't know how the commit comments can be retrieve to generate such a list (may be git and the wiki are able to communicate ?) but it was very difficult to get this information for 3.3, so we really need to think about it for the next release

* for QA:
- TCM is the most important tool we (l10n and QA groups) miss currently
- A kind of QATrack, not to track the release state like we did for OOo, but the QA state of the l10n builds is an important information provided by each team. May be that can be a part of the TCM (like a report, or such, in a table? I don't know) - A repository for VCLTestTool reports (if it makes sense to go on with running them of course)

* for L10n
- TCM also for dedicated tests on new features/localization. TCS localization will be managed on Pootle so no tools needed here, but the TCM should be able to handle localized tests. - may be a repository for the .sdf and the different tools we use and for the team who are not using Pootle.

For the TCM, I've already work on specs and the requests of the teams, so I can right in detail what we need and provide the TCS too. If I forgot something, don't hesitate to add it. Also should I add the list on the website page of the wiki?

Kind regards

Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.