> Which would include giving the "monkeys" complete access to the 37s > application code (because I think THIS is what all the patches get > tested against, I think). The problem is that there are tests which > are not included in Rails and are effectively proprietary, but 37s > (being the core maintainers of the framework) have the privilege of > verifying patches against their own applications before the patches > are rolled out.
> Not to offend anyone - just a thought. While 37 signals (and joyent, odeo, shopify, fluxiom etc.) have applications to support, the core team also has a commitment to rails itself. Part of that commitment is making sure that the tests in rails accurately reflect our own usage. If I find a change has broken something in joyent, I update the tests bundled with rails to cover that usage, so it doesn't happen again. David, Jamis, Marcel and Sam have the same responsibility, and do the same thing! If we commit something which passes the rails tests and basecamp breaks. Then sorry guys, that's Basecamp's problem ;). 2/3rds of the Rails core team work for companies other than 37 signals. The problem at present is that most of us are in the crunch phase of our applications, and we've fallen *way* behind on the patch queue. We realise that, it's not acceptable, and we're working to regain momentum. -- Cheers Koz _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
