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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/ironruby-core/attachments/20080326/2a9d8a81/attachment-0001.html
I agree, RubyForge seems to be woefully underutilized. It should be kept up to date and be THE resource for IronRuby development. On Wed, Mar 26, 2008 at 10:27 AM, Chris Chandler <chris at developingchris.com> wrote:> 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 > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >-- Michael Letterle [Polymath Prokrammer] http://blog.prokrams.com
Chris Chandler:> 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?Working on this right now. Thanks for the poke :)> 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.This might be too high of a bar given our current rate of contributions. That said, it would be awesome if folks could ping the list when the post a patch and reference the patch # in the ping. Thanks, -John
John Lam:> > 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? > > Working on this right now. Thanks for the poke :)Just finished triaging all of the open bugs. I closed a few after verifying the fixes but at least every bug has an owner. Will hopefully close some of the older / simpler ones today. Thanks, -John