Hi all,
first - thanks to Joost for this summary. And of course thanks to the
OOoCon06 team for this great event and all the people who have been
there (esp. those who are interested in QA ;-) ).
I'd like to add some comments to Joost's summary. (Esp. about things we
are going to work on in the future).
The first comments about the QA-work have been made at the Community
Council meeting (the first meeting at the Conference). Laurent raised
the issue, that QA work is often exhaustive, as we seem to duplicate
work. In many cases, the probel is that we do not know, what each other
is doing. This has been already adressed here at the list and some work
has been started (e.g. visible approval of RC's / automated test runs by
Sun). But I got the official activity item to improve the documentation
of the process.
Another idea has been initiated (or resuscitated) at the council
meeting: to implement a tool for collecting and analyzing results of the
automated testruns. As alredy mentioned by Joos, we (Joost, Laurent
Godard, Jörg Sievers, Thorsten Bosbach and me) had a a first
"brainstorming" session about that. As this idea has been filed as
Google Summer of Code Application, we should have a good starting point.
So we know about a similar tool, that is used inside Sun (we have ben
able to havea short look at the tool). Unfortunately, the technology
cannot be used outside Sun (as ist is proprietary and depends on the
local environment). But Sun agreed, that the tooling will be documentend
a a mentor was available. (In fact some parts are already documented).
We do have also a solution for the hosting at hand. So what we really
need is someone who is volunteering to implement this. Laurent is going
to see, if volunteers can be recruited at a nother project (the project
is about automated testing of OpenSource Software in general .. and
testing OOo would be some kind of prototype).
But If we have interested people here at the project, please raise your
hand ;-)
Furthermore, I was happy to meet Andrea Pescetti. Andrea is working on
the "QAtrack" tool, what is supposed to help with our release testing
and tracking the status of several builds. The tool description is
available at
http://wiki.services.openoffice.org/wiki/Release_QA_Tracking_Tool
The tool is almost functional at the moment (but needs testing,
debugging and some improvements). After some discussion with Andrea, we
agreed, that we should go on and try the tool for tracking the 2.0.4
Release status. This only will be a test run for the tool, but hopefully
we can collect enough feedback, so that the Release for 2.1 would be
more easy. (I'll write a separate invitation for testers.)
Best regards,
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
