> I added that because so often the answer given by projects to "these bugs > $are in STABLE" is "upgrade to $BLEEDING_EDGE".
Yeah, while we have a tradition of running on edge, I'm not going to suggest that it's a good practise though. > Okie. One question I forgot to ask before -- do we go through the +1 > process/verified process, or do I just set 'verified' immediately to get it > into the verified report (on the basis that, if the fix went into edge, the > patch is probably OK)? Should there be (is there) a tag specifically for > "this needs to be applied to the stable branch"? Nothing jumped out at me > in http://dev.ror.o/reports. Lets just use http://dev.rubyonrails.org/report/19 Tickets get there by being tagged with 'needs_review'. If the patch applies more or less cleanly, we can skip the review stuff, if the bug needs a wholly different fix we'll do some more rigorous reviewing. However I think that it's unlikely to be necessary. > I'll see what I can do in that line, but others should probably chip in > their favourites as well. Absolutely, people who have 'annoying bugs' they want fixed in 1.2.x should probably do some trac searching, or jump into #rails-contrib and ask around. Once we get a sense for the size of the problem, we can schedule a rough release date. -- 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 -~----------~----~----~----~------~----~------~--~---
