Who is in charge here? Presumably, many people; after all that is the open source way. However, like any engineering team with a collective goal there must be order and structure. But it seems we have left that up to a bug tracking system. We build new features faster then we fix old bugs. Bugs begin to build upon other bugs. DHH a few months back told me that the 37signals apps run from an almost bleeding edge version of rails. That was before 2.0 was released. I do the same with some of my apps today, and its been stable.
Naysayers who don't see the light, constantly pass Rails off as technology lacking robustness. Its just a tool to quickly mockup a website -- make a blog in 5 minutes. Ouch, those are the kinds of developers that learn Java in college or PHP from a web tutorial and proclaim mastery. Rails developers are programmers that are passionate about their craft. They understand the art form and continually push technology. 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. Regards, Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
