Hi,
The list would be flooded then.
Setting up CI doesn't mean we should receive a mail for each and every breakage (can be
some kind of digest, or a separate mailing list like on a couple of projects around).
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.
The plugins 'ecosystem' is still rather young. Not all the plugins authors
can guaranty they'll be able to maintain their work on the mid or long term.
Even without explicitely depending on implementational details, breaking
changes can be introduced, subtile side effects can lead to breakages, etc.
Just being aware of which changes cause trouble in the plugins ecosystem
can ease the everyday life of a Rails user, and at the end of the road, help gain
more traction to rails.
Anyway, thanks for your answers!
_______________________________________________ Rails-core mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-core
