When you are releasing an add-on and make changes on API, it is hard to keep compatibility, but it should be done.
Here you have changed the design of your add-on and move from a browserview to adapter. This kind of change is quite strange because adapter can not be directly used into templates and are really different from browser view. You should keep the browserview and make it use the adapter ! (Quite simple to achieve) We need upgrades when we make changes on default profile, so you are sure people who are using your add-on will be notified of changes in your add-on install method and will be able to upgrade just by pushing a button in the control panel. ----- Jean-Michel François aka toutpt http://toutpt.makina-corpus.org http://twitter.com/toutpt -- View this message in context: http://plone.293351.n2.nabble.com/Providing-backward-compatibility-for-a-zope-component-tp6345399p6348484.html Sent from the Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
