[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-dev] Closing bugs

We haven't used the closed state for Mylyn until now. I think in the past it limited what others could do on the bug (reassign, reopen) but I don't know if that still holds true. 

I think it's good practice to verify and close bugs for a release and we should get into that habit but I am not sure that the benefit would warrant making that a mandatory part of our workflow. I am fine if you want to do that for any bugs you are involved with though.


On Wed, Apr 11, 2012 at 9:20 PM, Torkild Ulvøy Resheim <torkildr@xxxxxxxxx> wrote:
Hi all,

I've been looking through some of my old bugs and noticed that only a few of them has been closed. I've checked the wiki and found this article about Bugzilla http://wiki.eclipse.org/Development_Resources/HOWTO/Bugzilla_Use. According to this the QA should verify and close the bug. Now that can put quite a lot of strain on the QA so I guess that's why we're not doing it. However I would like to put the bugs in closed state so that I can get them out of the way. Any ideas on how we should do this?

Best regards,
mylyn-dev mailing list

Steffen Pingel
Senior Software Developer, Eclipse Mylyn
Mylyn Tasks Lead