Hi, -------- Original-Nachricht -------- > Von: Joost Andrae <[email protected]>
> > > > 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. No, I'm not missing thiat point - but this is diferent from my point. The QA rep for a CWS comes into play, when the developer has done his job (at least this is what is communicated at the wiki). But the preparation of the CWS (which bugfixes should go in) is unclear and seems mainly be the task of the developer. I think, QA team can help a lot here. ... > > > 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 ? As said - if we have the commitment from development, that there will be a joint effort to fix those bugs - yes. If this works well (and I really expect this), I'd suggest to do this more often and for other topics as well. André -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
