On Jul 14, 2:44 am, Pratik <[EMAIL PROTECTED]> wrote:
> Sounds cool.
>
> You can probably mention #rails-contrib as well for finding potential
> reviewer.
>
> And how about having a rule to close the ticket as invalid/wontfix if
> it's been there for over 2-3 months without any updates ? And may be
> get a core member to reopen it if one feels the patch has a chance of
> making it to core ever. I was just going through some of the old
> tickets, and I feel that very small % of them will ever make it to
> core. Probably closing the remaining tickets would be good to keep
> things clean on trac as some of them are even 2 years old.
Hi, is it feasible to add a 'tiimeout/stale' option for the closing,
rather than invalid/wontfix. At least then you'd be able to see more
accurately why something was closed ? It also opens up the
possibility of having a bot of some sort just sweep daily and time
things out (while still retaining some traceability of the fact it was
auto-closed rather than manually closed).
A.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---
