Hi *, On Fri, May 21, 2010 at 3:49 AM, Thorsten Ziehm <thorsten.zi...@sun.com> wrote: > Jan Holesovsky schrieb: >> On Thursday 20 May 2010, Thorsten Ziehm wrote: >> >> As I wrote below "if you find out that a bug is invalid in up-stream, but >> the reporter talks about a particular Linux distro" - no additional >> turnaround. The info is not there => invalid, the info is there => >> go_oo_bugs. > > I'm fine with it, as I wrote some mails ago. Existing issues and wrongly > written issues in IZ can be handled by QA community members as you > requested.
+1 > But I do not want to have Issues from Ubuntu, go-oo or any > other company, which release a different product and which use the name > of OOo only. > [...] ++++++1 Accidentally filed issues are OK, they don't need to be flagged "invalid", if only to not hurt the feelings of the reporter. But it should be avoided to have every distro-OOo-user file the bugs in issueZilla. Also as noted before: There are many of them. If the go-oo alias will be a black hole similar to requirements, with no visible action on those (be it because a duplicate is filed in the distro's bugtracker already and handled there), or just because nobody is there to look at them, not much is helped. So far I read support for the user-alias from the novell-Part of go-oo, but no statement of the other distro's representatives. Especially none of ubuntu that were the starting point of this thread. And especially as Charles wrote: ## [why doesn't ubuntu raise the quality of their builds to that of vanilla OOo] # Because they don't have the necessary resources and they don't have the skills. Plus, it's very # much unclear whether these are always distro-specific bugs, that's part of what we're trying to # discover. So if they lack resources to deal with their own issues, I'm not sure they'll find resources to deal with issues not filed into their own tracker. Bottom line is: If there is no support for this way of dealing issues by all of go-oo, then it's not worth the effort, then closing as invalid with a comment to file in the distro's tracker instead is the better way IMHO. Or if you prefer, a different resolved state doesn't have a negative connotation like invalid. Be it "nonvanilla" or something. If the issue is important enough for the user, the user will file a new issue. If it is too much effort, the issue isn't worth the time anyway. (yes, there are exceptions, but basing a process on those exceptions is again the wrong approach) OOo doesn't suffer from too few issues to deal with after all. ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qa.openoffice.org For additional commands, e-mail: dev-h...@qa.openoffice.org
