On 2/8/06, Rick Olson <[EMAIL PROTECTED]> wrote: > > 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.
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. 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. Kev _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
