Re: [Libreoffice-qa] REPOENED Status

2014-08-02 Thread Bjoern Michaelsen
On Sat, Aug 02, 2014 at 07:14:59AM -0700, Pedro wrote: > I also realize that Developers prefer that Bugs should not be REOPENED > because it is unlikely that the bug a user finds now is exactly the same > problem that was solved before (even if the apparent result is the same and > therefore the bu

Re: [Libreoffice-qa] REPOENED Status

2014-08-02 Thread Bjoern Michaelsen
On Sat, Aug 02, 2014 at 10:34:01AM +0200, Florian Reisinger wrote: > The bigger problem is the following: > User A submitted a bug #123. A QA closes this bug as RESOLVED WFM. User A > disagrees and puts the state to > 1) REOPENED > 2) NEEDINFO > > Sorry to say, but this "error" will continue...

Re: [Libreoffice-qa] REPOENED Status

2014-08-02 Thread Pedro
he user can change to MOREINFO, and adds additional info. -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-REPOENED-Status-tp4117474p4117552.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Lib

Re: [Libreoffice-qa] REPOENED Status

2014-08-02 Thread Tommy
On Sat, 02 Aug 2014 11:00:09 +0200, Pedro wrote: Florian Reisinger wrote The bigger problem is the following: User A submitted a bug #123. A QA closes this bug as RESOLVED WFM. User A disagrees and puts the state to 1) REOPENED 2) NEEDINFO Sorry to say, but this "error" will continue...

Re: [Libreoffice-qa] REPOENED Status

2014-08-02 Thread Tommy
On Sat, 02 Aug 2014 10:34:01 +0200, Florian Reisinger wrote: Hi, The bigger problem is the following: User A submitted a bug #123. A QA closes this bug as RESOLVED WFM. User A disagrees and puts the state to 1) REOPENED 2) NEEDINFO Sorry to say, but this "error" will continue... Liebe G

Re: [Libreoffice-qa] REPOENED Status

2014-08-02 Thread Pedro
BAD option... Just my 2 cents. -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-REPOENED-Status-tp4117474p4117517.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Libreoffice-qa mailing li

Re: [Libreoffice-qa] REPOENED Status

2014-08-02 Thread Florian Reisinger
Hi, The bigger problem is the following: User A submitted a bug #123. A QA closes this bug as RESOLVED WFM. User A disagrees and puts the state to 1) REOPENED 2) NEEDINFO Sorry to say, but this "error" will continue... Liebe Grüße, / Yours, Florian Reisinger > Am 02.08.2014 um 08:44 schrieb To

Re: [Libreoffice-qa] REPOENED Status

2014-08-02 Thread Jochen Schiffers
Hi Joel, Good post. I have installed your note in the German Wiki. Regards Jochen Am 01.08.2014 18:34, schrieb Joel Madero: Hi All, I'm noticing quite a few QA members using REOPENED incorrectly so this is just a reminder. REOPENED is for a bug that has been marked as FIXED by a develope

Re: [Libreoffice-qa] REPOENED Status

2014-08-01 Thread Tommy
On Fri, 01 Aug 2014 19:43:06 +0200, Joel Madero wrote: Hey Florian, Hi Joel, I do not remember any direct way from WFM to UNCONFIRMED. I have not done much lately, but REOPENED was the only "meaningful" way to get it out of resolved state... Anyway, thanks for highlighting :) Yeah -

Re: [Libreoffice-qa] REPOENED Status

2014-08-01 Thread Joel Madero
Hey Florian, Hi Joel, > > I do not remember any direct way from WFM to UNCONFIRMED. I have not done > much lately, but REOPENED was the only "meaningful" way to get it out of > resolved state... Anyway, thanks for highlighting :) > Yeah - best to go from WORKSFORME to NEEDINFO and then to UNCONFI

Re: [Libreoffice-qa] REPOENED Status

2014-08-01 Thread Florian Reisinger
Hi Joel, I do not remember any direct way from WFM to UNCONFIRMED. I have not done much lately, but REOPENED was the only "meaningful" way to get it out of resolved state... Anyway, thanks for highlighting :) Liebe Grüße, / Yours, Florian Reisinger > Am 01.08.2014 um 18:34 schrieb Joel Madero

[Libreoffice-qa] REPOENED Status

2014-08-01 Thread Joel Madero
Hi All, I'm noticing quite a few QA members using REOPENED incorrectly so this is just a reminder. REOPENED is for a bug that has been marked as FIXED by a developer and is currently assigned to that developer. It is *not *for a bug that has been marked as WORKSFORME (ie. never confirmed or a bug