Re: [Development] QtCS2014 - Expiring bug reports
Am 18.06.2014 11:09, schrieb Oswald Buddenhagen: On Tue, Jun 17, 2014 at 06:31:45PM +0200, Robert Löhning wrote: By the way: What will happen to bug reports from now closed identities? i'm inclined to change the reporters (and assignees) to the new accounts. it isn't exactly rocket science, only a bit of work... This sounds great! ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtCS2014 - Expiring bug reports
On 17/06/14 18:31, Robert Löhning robert.loehn...@digia.com wrote: Am 17.06.2014 18:04, schrieb Thiago Macieira: Em ter 17 jun 2014, às 13:51:37, Robert Löhning escreveu: we mostly already agreed on this at QtCS so I'd just like to stress one point: old should not mean the time passed since creating the bug report. There are bugs which have been listed for a long time but are still actively discussed. Old in this context should mean the time since the last comment, status change asf. So the nice comment would come after 1 year of silence and the report would be closed after nobody replied to that comment for three months. I assume you meant that anyway? Yes. Old as in inactive for a long time By the way: What will happen to bug reports from now closed identities? The reporter won't get any notification and I'm afraid the watchers won't feel addressed by the Need more info comment. Simple. If nobody feels inclined to do anything, the bug will eventually get closed. Cheers, Lars ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtCS2014 - Expiring bug reports
On 18/06/14 11:09, Oswald Buddenhagen oswald.buddenha...@digia.com wrote: On Tue, Jun 17, 2014 at 06:31:45PM +0200, Robert Löhning wrote: By the way: What will happen to bug reports from now closed identities? i'm inclined to change the reporters (and assignees) to the new accounts. it isn't exactly rocket science, only a bit of work... For those where there is a new account I’m all for doing that. Cheers, Lars ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtCS2014 - Expiring bug reports
On 18 June 2014 07:15, Knoll Lars lars.kn...@digia.com wrote: On 17/06/14 18:31, Robert Löhning robert.loehn...@digia.com wrote: By the way: What will happen to bug reports from now closed identities? The reporter won't get any notification and I'm afraid the watchers won't feel addressed by the Need more info comment. Simple. If nobody feels inclined to do anything, the bug will eventually get closed. Even simpler, when changing the status to Need more Info if the reporter account is marked as Inactive/Closed, then note that fact in the message and tell the watchers they they need to take action. In fact, when writing the Needs Info message on any bug the request should be addressed to all the watchers rather than just the reporter, seeing as very old bugs are likely to have bouncing reporter email accounts. And +1 to transferring to new accounts where they exist. John. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtCS2014 - Expiring bug reports
Am 15.06.2014 02:40, schrieb Thiago Macieira: We had a session on expiring bug reports again. Here are my notes: * Bug database is cluttered with old stuff * Only triagers and devs can re-open bugs ** Normal people can only clone bugs * Process: ** For *Unassigned* bugs that are 1 year old or more, post a nice comment saying we're sorry we didn't get to it and ask for re-confirmation ** Move the bug to Need More Info state ** Send a list of bugs that changed state sorted by priority (especially P0- P2) ** Every month, expire Need More Info bugs that are 3 months old ** For the first time, we'll start with longer periods, then shorten to the numbers above * Assignment process: ** Assignee is the person who is going to do the work, conceivably in the near future ** If you're not going to do work, unassign, *but keep watching* ** All bugs need to have at least one watcher ** All components must have a default assignee, who triages * This applies to Qt only, not Creator * This applies only to Bugs, not Tasks or Suggestions Link: http://qt-project.org/groups/qt-contributors-summit-2014/wiki/Expiring_Bugs Hi Thiago, hi list, we mostly already agreed on this at QtCS so I'd just like to stress one point: old should not mean the time passed since creating the bug report. There are bugs which have been listed for a long time but are still actively discussed. Old in this context should mean the time since the last comment, status change asf. So the nice comment would come after 1 year of silence and the report would be closed after nobody replied to that comment for three months. I assume you meant that anyway? Best regards, Robert -- Robert Löhning, Software Engineer - Digia, Qt Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtCS2014 - Expiring bug reports
Em ter 17 jun 2014, às 13:51:37, Robert Löhning escreveu: we mostly already agreed on this at QtCS so I'd just like to stress one point: old should not mean the time passed since creating the bug report. There are bugs which have been listed for a long time but are still actively discussed. Old in this context should mean the time since the last comment, status change asf. So the nice comment would come after 1 year of silence and the report would be closed after nobody replied to that comment for three months. I assume you meant that anyway? Yes. Old as in inactive for a long time -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtCS2014 - Expiring bug reports
Am 17.06.2014 18:04, schrieb Thiago Macieira: Em ter 17 jun 2014, às 13:51:37, Robert Löhning escreveu: we mostly already agreed on this at QtCS so I'd just like to stress one point: old should not mean the time passed since creating the bug report. There are bugs which have been listed for a long time but are still actively discussed. Old in this context should mean the time since the last comment, status change asf. So the nice comment would come after 1 year of silence and the report would be closed after nobody replied to that comment for three months. I assume you meant that anyway? Yes. Old as in inactive for a long time By the way: What will happen to bug reports from now closed identities? The reporter won't get any notification and I'm afraid the watchers won't feel addressed by the Need more info comment. Best Regards, Robert ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
