Hi,
The great strength of iTeams is, that the team members cover
the full development process. Work can be done in collaboration
and with common understanding what to do an why (or why not to do
something else).
Using iTeams for Features and Enhancement implementation is really
useful and it already is an established way to work on implementations.
I'd be happy to be corrected here - but iTeams focus on new features.
There is nothing like iTeams for bugfixing. That means - for bugfixing
we have no common understanding why we fix what we fix - and why we
don't fix what we do not fix.
One of the first steps an iTeam does for a new fetaure is to collect
the related issues and requirements. This is (or at least seems to be)
missing for bugfixes.
You're missing the point here because for bug fixes we have the
developer and a responsible QA representative working on the child
workspace that is used to integrate the bugfix.
Martin Hollmichel once mentioned, that commented issue lists like
http://wiki.services.openoffice.org/wiki/User:Lendo/Usability
might be very helpfull.
it is
or have a look at
http://wiki.services.openoffice.org/wiki/Arabization_efforts which I
used to track issues that were needed to coordinate the planning of
Arabic localization and internationalization for OpenOffice.org 3.1.
This document was used as a helper. Later we used a keyword in IssueTracker.
I agree here and would see such a focused and commented list as
starting point for some focused bug fixing efforts. I'd really love
to work on something like this - as long as it is somehow within
my experience and developers would join.
Would you like to help Jaqueline with collecting issues regarding "mail
merge" and "numbering" in Writer like we already discussed at the QA
weekend in Essen ?
Kind regards, Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
