Hi Thorsten, On Thursday 20 May 2010, Thorsten Ziehm wrote:
> Perhaps I misunderstood the releases of go-oo. In the following blog > you can find links, what is/isn't contributed to OOo. As you can see > the products are differ in parts a lot. > > http://lizards.opensuse.org/2010/05/17/openoffice_org-3_2_1_1/ http://cgit.freedesktop.org/ooo-build/ooo-build/tree/patches/dev300/apply is the ultimate source of the information what has been contributed, search for "i#" in there, this means that the patch has been filed to the up-stream IZ. As I explained, our process involves filing patches to the IZ for up-stream bugs we find (or creating CWSes when appropriate), if you find out that it hasn't happened in some case, please let me know, we must fix that. > How often the QA person should go in contact with the bug reporter to > get the feedback that is a bug in Ubuntu or any other distro version? > This is the time which costs resources. 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 would like to ask you to try the alias solution I proposed. I have > > just created a go_oo_b...@openoffice.org user; if you find out that a bug > > is invalid in up-stream, but the reporter talks about a particular Linux > > distro (openSUSE, Debian, Ubuntu, ...), just reassign it to > > go_oo_b...@openoffice.org, instead of setting it as 'invalid'. The > > notification will go to our mailing list (ooo-bu...@lists.freedesktop.org > > at the moment, and I asked for a dedicated one), and no other work for > > you - we will take care of the rest. > > Do you know, how many issues we talk about currently? Near to 600 issuer > are set to invalid or worksforme since begin of 2010. And I heard by > some of my QA engineers, that these issues are often for OOo versions of > other distros. Then if they get fixed, you'll get no other duplicates :-) But if we don't know about them [instead of reporting to the go-oo (Novell) bugzilla, the reporter chose up-stream IZ, and it was done 'invalid' there], how can we help you to get the number down? > If you want to get a feeling, what the situation is. Please query for > all invalid issues from the past month. Evaluate them and evaluate if > these issues are in 'not-vanilla' OOo versions are only. I looked, and eg. http://www.openoffice.org/issues/show_bug.cgi?id=111606 is a perfect example. Instead of: 'For help and support please use the us...@openoffice.org mailing lists. Please also check if this also happens in the OOo version from our site. If not, please report this to Ubuntu.' + setting to closed invalid you'd do: 'For help and support please use the us...@openoffice.org mailing lists. Please also check if this also happens in the OOo version from our site. Looks go-oo related though, reassigning.' + reassign to go_oo_bugs. > > Do you think it might work for you, please? > > If a process of handling such issues (I wrote about it some mails ago) > exists and the alias aren't a black hole where nothing happen, than it > might work. But it still costs resources in the mother-project OOo. And > this I want to avoid. No, it is not going to be a black hole. I just hope my proposal is the least work for you, with potential benefits for all of us. All the best, Kendy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qa.openoffice.org For additional commands, e-mail: dev-h...@qa.openoffice.org
