There are a lot of bugs on the rubyforge tracker system, as well as patches for some, and some that have been found invalid.
Can we cleanup rubyforge tracker/patches? Is the tracker being used internally by the IronRuby Team? Should we adopt a patching system at least socially like rails? For those not used to the rails patch process. Basically three community members must comment on the ticket that the patch runs for them when applied to the current svn repository. This allows the submitter to put a tag on the ticket which puts it in a priority 1 report for the core team to apply within the next cycle, usually within the next week. There are also other report queues that have corresponding tags so that they can clean up bad patch bug combo's. -- Thanks, Chris Chandler
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
