> Rails is completely opensourced under the MIT license as far as I > know. There shouldn't be proprietary tests. Testing against > applications is good, but really, that is what unit testing is used > for in the codebase.
Amen. > Merge monkeys isn't necesarily the best course of action though. Does > anyone have a better idea? Can we hear the opinion of someone on the > core team? It's just us talking amogst ourselves and wishful thinking > until one of you says something. Merge monkey's is: 1) an insulting name 2) solving the wrong problem. We're looking at ways to get more granular with patches. Currently 2 line patches which fix a small bug appear in the same queue as massive feature additions which touch every part of rails. Similarly, spelling errors show up alongside complicated bugs relating to big nested object graphs. I think getting more granularity in the queues is the first step. Any thoughts? -- Cheers Koz _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
