I had a discussion with Irina and Olena this morning and our suggestion is to update the deprecation warning to be explicit - i.e. if you are installing a plugin from scratch on MOS 6.1, it should say something to the effect of DEPRECATION WARNING: this plugin is incompatible with MOS 6.1 - please go to Fuel Plugin Catalog {link} to see if an updated version is available.
I think there is still work to be done on testing the upgrade use case with plugins (Oleg is documenting this/working on this now), but agree that making a previously compatible plugin unusable because the MOS version has been changed doesn't make much sense.
Fabrizio - would a more explicit deprecation warning be sufficient, from your perspective?
I had a discussion with Irina and Olena this morning and our suggestion is to update the deprecation warning to be explicit - i.e. if you are installing a plugin from scratch on MOS 6.1, it should say something to the effect of DEPRECATION WARNING: this plugin is incompatible with MOS 6.1 - please go to Fuel Plugin Catalog {link} to see if an updated version is available.
I think there is still work to be done on testing the upgrade use case with plugins (Oleg is documenting this/working on this now), but agree that making a previously compatible plugin unusable because the MOS version has been changed doesn't make much sense.
Fabrizio - would a more explicit deprecation warning be sufficient, from your perspective?