> But now .. the bug in this posting, which will affect anyone including > two associations, has been neglected for almost a month. What > irritates me is that a patch has been ready hours after the bug was > discovered, yet the five letters ".chop" at the end of line 23 still > have not been amended. Obviously it was forgotten in the shuffle of > more exciting work such as building new features. But features are > thrown out the window if you cant maintain robustness in the process.
Peter, As I mentioned earlier in this thread this ticket now has more than 20 patches, and more than 50 comments, it's impossible for someone new to this issue to figure out what is going on, let alone review the patches and apply them. What's needed are *new* tickets for each of the bugs found, so that the review and commit process is simpler for everyone concerned. As someone who clearly knows what's going on, perhaps you could create a new ticket, and upload the relevant patches to it? Two weeks ago I mentioned the best way forward to getting these patches applied, frederick followed up with some more information. Let's do that rather than getting indignant about new features and robustness. -- 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 -~----------~----~----~----~------~----~------~--~---
