On 6/7/2010 8:08 AM, Douglas Hubler wrote: > I checked a few issues that where closed based on their reported date > being before a certain date and the few that i checked were still very > real and very useful. Can we organize a crowd-souring effort to > review bugs so we don't have to automatically close things? > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > Most of the issues are old and have no hope in getting addressed in the near term. To be clear nothing was closed only put into a won't fix state. This allows the owner to re-open the issue and if someone feels strongly about an issue closed I encourage them to re-open it.
What is a problem is carrying around 1000+ issues in the backlog with many from people who no longer are even working in the industry. The backlog should represent issues that at some point will get addressed. that being said I like your suggestion of a review. Let me see what we can setup to do this. I would say lets review more than anything close but also anything without a fix version. Make sense? Al _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
