This would be a little overzealous because plugins might require 3rd party libs. Besides, for example one of my plugin just bails out because of recent changes in Ferret - not "throws" but really _bails_ at some deep and dirty C level. The list would be flooded then.
Additionally, most plugin breakage is intentional. If a plugin depends on implementational details, then it'll naturally break when those change. So it falls on the back of the plugin creator to continuously update and verify his plugin against the latest Rails. So I do encourage that plugin developers setup CI services, the information is just only useful to them, not to the core team. -- David Heinemeier Hansson http://www.loudthinking.com -- Broadcasting Brain http://www.basecamphq.com -- Online project management http://www.backpackit.com -- Personal information manager http://www.rubyonrails.com -- Web-application framework _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
