On 6/2/06, Thibaut Barrère <[EMAIL PROTECTED]> wrote:
If all this already is available, I'll be happy to use it. If not, would there be some interest in it ?
Thibaut, As a regular rails user, I'd certainly be happy if you were to pursue this. Would be a lot of work though, as you'd most likely want to test each plugin individually against the new rails checkin (as some plugins conflict with each other), many plugins require some manual setup (creating new tables, adding columns to your other tables, creating a set of models and controllers that can use the new functionality, etc), and most plugins don't already include tests to check if they are working correctly, so these tests would need to be written. But even test coverage of some the plugins would be better than no coverage. =) And if you created this framework for testing the plugins, it might encourage the plugin authors to include test apps for their plugins. Your testing framework could get updated about new checkins by subscribing to the rss feed off trac, so you wouldn't need the core team to do anything for you to get started with this. If you do go forward with this, you might want to get in touch with Benjamin Curtis of http://www.agilewebdevelopment.com/, as it seems like this plugin directory would be a great place to update the status of the tests of the plugins. If plugins authors and users are notified quickly that new rails code breaks their plugin (and exactly what checkin breaks them), it should help to keep plugins up to date with the current rails trunk. You should propose this on the main rails list, or just go ahead and do it and ANNOUNCE it on the main rails list. =) - Isaac _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
