Re: [Libreoffice-qa] What are the requirements to set a bug to NEW
Hi Robert, Op 10-02-13 12:07, Robert Großkopf schreef: Hi *, I 'm just looking for some bugs in Base. There I found bugs declared as NEW, where nobody else but the report had made a comment and nothing is to see in the history about anybody, who has switched the report to NEW. This bug I have set to Needinfo. Was set to New. Could only be set to New by the reporter. Indeed, following the 'history' https://bugs.freedesktop.org/show_activity.cgi?id=60217 it's set to NEW when it was submitted. https://bugs.freedesktop.org/show_bug.cgi?id=60217 I thought there must be someone, who could confirm the bug - not only the reporter. Or could we confirm our bug by ourselves? Also correct; It's not the right workflow to 'confirm' your own bugs. Only (core) developers (or very experienced QA members) can set a bug to NEW without confirmation. Unless they are looking for a 'second opinion'/independent confirmation. You did good to set the bug status to NEEDINFO because there is not enough info to confirm this bug. The problem with this kind of bugs is that: when someone set the bug status to NEW or RESOLVED WORKSFORME, we can't set it back to UNCONFIRMED (because the system mark it intern as 'ever reproduced = 1'). I also see that this bug is reported directly to FDO. With our BSA, where most people and end users report a bug, isn't this easy/possible anymore to set your bug while submitting to NEW (unless they browse afterwards to their own bug, log in to FDO and set it as NEW). Thanks for this cache, and you did great and correct :-). Kind regards, Joren ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] What are the requirements to set a bug to NEW
Robert Großkopf schrieb: Hi Robert, the general condition for NEW is that information the Bug report is complete and reliable so that a developer can start with hacking without need to do additional basic research. The most important info is short, but clear instruction how to reproduce the problem We have some brief hints here https://wiki.documentfoundation.org/QA/BugTriage#Set_Status_.26_Prioritize what should get some more detailed completion on QA-FAQ with some kind of check list, I will start a draft next days. So I completely agree with your concerns and Joren's notes concerning Bug 60217: we need more info there. Although we have some tendency to to lower the bar for NEW because there is some danger that a Bug too often becomes visited without possibility to add more info (where a developer might be able to find out the missing info very quickly), a clear instruction is mandatory. Best regards Rainer ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] Bugs and Fixed Resolved Closed status
I am just going through some bug fixing and stuff, and, I was wondering if this were possible. Some of the bugs are being redirected to the lists. This is really helpful and, in my experience it works at mobilizing the teams to work on them. I was wondering, would it be possible to make it so that when a bug has reached the status of Fixed and/or Resolves and/or Closed, would it be possible for this to trigger Bugzilla to email back to the list of its ClosedFixedResolved etc. status? It would be neat if the teams had a report for when the bug was no longer in need of attention. Cheers, Marc -- Marc Paré m...@marcpare.com http://www.parEntreprise.com parEntreprise.com Supports OpenDocument Formats (ODF) parEntreprise.com Supports http://www.LibreOffice.org ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Bugs and Fixed Resolved Closed status
Marc Paré schrieb: I was wondering, would it be possible to make it so that when a bug has reached the status of Fixed and/or Resolves and/or Closed, Hi Marc, I think the way how that can be done most easily is that someone who maintains the bugs.freedesktop.org account for the mailing list adapts the mail preferences (checks 'Get mail when The bug is resolved or reopened'. For needs what can not be fulfilled by list owners please simply submit a LibO-WWW-Bugzilla bug with Importance enhancement. Best regards Rainer ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
