Yes because they were set to REOPENED incorrectly. REOPENED has a specific definition and they were incorrectly there. Furthermore, some of those bugs were "self confirmed" which we recommend against. That being said, if a bug is confirmed and I set it to UNCONFIRMED just set it to NEW and move on....there were 350+ bugs incorrectly set...you'll see more moving to UNCONFIRMED if they were set incorrectly to begin with. Also the comments that you points out didn't clearly confirm the bugs that I asked. Anyways, expect more.
Best, Joel On 11/04/2014 01:13 AM, Cor Nouws wrote: > Hi Joel, > > Joel Madero wrote on 04-11-14 04:47: > >> So I just booted about 50 bugs over to UNCONFIRMED so that list has >> jumped. I'm going through the rest of the list of about 280 more bugs - > > Sorry that I'm not fully aware of what's going on here, but I'm rather > annoyed by the fact that bugs that I have spend precious time on in the > past, to test and confirm, now are reset to unconfirmed... > e.g. 35275, 35917, 35954, 83373. > > If the goal is that the issues are retested for some reason, then pls > indicate that. Or do it yourself. > > Thanks! > > _______________________________________________ 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/
