[Insight-developers] Mantis bug list

[Hans Johnson]

David,

Thank you for you response.  Feel assured that you are not the only person
to express this opinion.

I strongly agree that there is a need for a better way to separate things to
get them out of the way, but there is nothing that has worked so far.  The
problem is that there is currently no place to put these items out of the
way, and the massive backlog of un-addressed issues has jeopardized the
utility of the entire bug tracking system.

There were many issues and feature requests that were ill defined AND
completely inactive for several years AND not assigned to any developer.  If
an issue gets closed that still has relevance, please re-open it with a
comment describing why it is important.

It was necessary to find a course of action within the scope of the
available resources.  Unfortunately, this required taking a sub-optimal plan
of action.  

===  Call to action ===
Please feel free to assign bugs you are interested in to yourself.  You
could take some of those stagnant feature requests and make in Insight
Journal article out of them, or take one of the ill defined bugs, and make a
patch set that demonstrates the error (or fixes the problem).


Regards,
Hans

-- 
Hans J. Johnson, Ph.D.
Assistant Professor
200 Hawkins Drive
T205 BT, The University of Iowa
Iowa City, IA 52242

hans-johnson at uiowa.edu
PHONE: 319 353 8587


On 11/7/10 10:01 AM, "David Doria" <daviddoria at gmail.com> wrote:

> On Sun, Nov 7, 2010 at 8:47 AM, Hans Johnson <hans-johnson at uiowa.edu> wrote:
>> ITK Developers,
>> 
>> There has been a lot of action on the Mantis Bug tracker lately.  We have
>> been working hard to get the bug list under control.   Over the past 2
>> weeks, we have cleared several hundred bugs.  As a second effort, we have
>> been looking at all the bugs, and trying to assign them to the team who most
>> needs to know about the issues.
>> 
>> Please review bugs assigned to you, many of them can simply be closed
>> stating that ITKv4 is addressing these issues, or that the will never be
>> addressed.
>> 
>> Hans
> 
> I applaud this effort, nice work! However, I disagree with the "this
> will never be addressed" idea. Just because a few people decide an
> issue is not high priority, that doesn't mean that it is not something
> that many users may still want. Leaving feature requests open may
> catch a developers interest in the future. Maybe there is a better way
> to separate these things to "get them out of the way", but just
> closing them I don't think is the right way to go.
> 
> David