Jeroen van Meeuwen wrote: > On Saturday, August 18, 2012 06:45:56 PM Jekyll Wu wrote: >> On 2012年08月18日 17:54, Myriam Schweingruber wrote: >>> Well, then reassign all those wishes to Kmail2. Seriously, you are not >>> making triaging easier. What on earth is wrong in asking the users >>> politely to reopen the wish in kmail2 if it is not yet implemented >>> there? I see nothing wrong in asking the users do a minimum of work >>> here >> >> One potential problem is many users do not understand the workflow of >> bugzilla and do not know how to reopen and reassign a bug to the >> "kmail2" product. Some may leave a comment saying the wish is still not >> implemented and wait for triageers/developers to do the reopen work, but >> some may simply feel frustrated and do not bother checking and leaving a >> comment. >> >> So although reopening is a easy work for developers/triageers, it might >> be a hard work for users. Maybe you can add/resend a short message to >> all those closed wishes about how to reopen and reassign the report to >> "kmail2" ? >> > > Rather than speculating what might or might not be hard work for a user... > there's thousands of them and dozens of us - I'm being optimistic in that > last > estimation. > > What MUST happen is clear, however. > > If Bugzilla is not cleaned up, it can only come to a grinding halt. That's > not > a performance thing, but a usibility thing that applies to both users and > developers; administrators, triagers and others notwithstanding.
Let me point out that the only issue raised in this thread is about WISHLISTS, not "normal" bugs. A good workflow that I have seen is to put a NEEDINFO first and then after a while close the bug. That can be easily automated. But this CLOSED (for kmail1 wishlists) arrived unexpected. Regards -- Luigi _______________________________________________ Kde-testing mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-testing
