On Fri, Jul 13, 2007 at 10:04:40PM -0700, Josh Peek wrote: > Maybe expand on the warning bitsweat added to the trac home page. > > "Expect your ticket to be closed with an untested, undocumented, or > incomplete resolution if it's missing tests, documentation, or > implementation. Don't panic; the ticket hasn't been killed! These > resolutions are the pathway to commit. Update your patch and reopen > the ticket."
This seems heavy-handed for patches which fix defects. I mean, if a defect report didn't have a patch at all, it'd stay open, but if it's a *better* report (ie closer to being fixed, just not quite all the way there) then it gets closed? That seems... counterproductive. (Disclaimer: I'm not a neutral party on this topic -- I've had a couple of bugs with patches treated this way recently; it *really* made me less interested in contributing future patches). 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? Also, I presume that this PatchProcess page will be rolled into or otherwise linked from http://dev.rubyonrails.org once it's considered acceptable? - Matt -- "For once, Microsoft wasn't exaggerating when they named it the 'Jet Engine' -- your data's the seagull." -- Chris Adams --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
