Hello KP, > Promoting QA in community is not enough - you have to retain people. In > order to retain people project needs to fix their issues, which inspires > people to use milestones in daily work. > Many of developers do not know how great it feels when issue you are > interested in gets fixed relatively quick. Developers also do not know > that it sucks when fix for your issue is delayed and delayed.
I'd claim a lot of developers, if not most, know how this feels - in both ways. It's just that we have much more issues than developers, and developers have only a pretty small amount of time for "fixing for retaining people". In combination, this might look like developers do not care for the issues reported by other people, but it's just not as easy as this. > I think many users would rather have faster fixes than more stable > milestone (you always can go to prev release/milestone). Uhm, I doubt that. What you're saying here is that we should sacrifice quality to more fixes. I believe this would be bad for OOo's overall reputation. Ciao Frank -- - Frank Schönheit, Software Engineer [email protected] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
