> I understand why patches get triaged, and > there is the possibility of bad patches hanging around forever, but surely > the policy of expiring old bug reports could also apply to half-baked > patches, rather than instant closure?
It's not just the possibility of patches sitting around, we had hundreds of patches just sitting around and the submitters commented that the lack of feedback was more frustrating than having a patch 'rejected'. What was it about the closure that made it irksome? Tickets get reopened all the time, closure isn't a death sentence. But it's more honest than just having an atrophied patch sitting in the queue. > Also, I presume that this PatchProcess page will be rolled into or otherwise > linked from http://dev.rubyonrails.org once it's considered acceptable? Yep. > - Matt > > -- > "For once, Microsoft wasn't exaggerating when they named it the 'Jet Engine' > -- your data's the seagull." > -- Chris Adams > > > > -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
