On Wed, Mar 2, 2011 at 12:35 PM, Gilles Lenfant <[email protected]> wrote: > Le 1 mars 2011 à 18:34, Suresh V. a écrit : > >> Plone 4 main_template defines new slots: >> >> content-title >> content-description >> content-core >> >> It would be better if we used these slots rather than fill the main slot as >> was done previously. This would reduce the duplication of all the viewlets >> code and also make it work better with changes in the main_template. >> >> But this would break Plone 3 compatibility. The trunk is already Plone 4 >> compatible. >> >> Is it ok to make these changes on the trunk and forsake Plone 3 >> compatibility on the trunk. Plone 3 users can always use the released >> version of the software. Versions up to 2.2 would work with the trunk. >> >> If no one objects, I will commit the changes on the trunk. > > And please don't forget to mention in README.txt that Plone 3 compatibility > is broken. And what version should be pinned for Plone 3 sites maintainers. > > As part time Plone 3 sites maintainer, I'm somehow tired to grep the SVN or > test various versions to guess what's the best suited version of such or such > component with Plone 3. >
Another thing I really like (but few Plone product do this) is to not publish on pypi only the last working version of the product auto-hiding others (I mean, when you plan to release it): For example - http://pypi.python.org/pypi/Plone -- -- luca _______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/product-developers
