I have added a new Resolution type to the project issue tracker:
"Retired". The description of this status is:
This issue has been closed because there has been no activity on
it for a long time. This does not represent a judgment that it
does not have merit, it's just a matter of housekeeping - if
someone feels that the issue should be Re-Opened, they may do so
without prejudice (and that counts as activity, resetting the
clock). The definition of "a long time" is deliberately vague.
We currently have 117 issues in the sipXecs project tracker that I
consider candidates for Retired status by this filter: Not Updated in >
1 year, and no Fix For Release value. That filter is available for your
perusal: http://tinyurl.com/cv5rox (name 'sipXecs retirement
candidates').
On Thursday, I will Retire (Resolve with 'Retired' status) any that are
still on that list. As noted above - that does _not_ mean that they
can't be reopened later, it will just help reduce the clutter in the
tracker. A quick look shows many that I think are no longer relevant,
possibly some that have been fixed under some other issue, etc. Many
open source projects do this, and I think that doing it around the time
we do releases is a good idea.
I plan to make a pass through looking for any that _I_ think should be
saved (I know there are some) and update them to get them off that list.
I know that there are some I want to save. If you have favorites that
are on there - touch them before Thursday morning.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
