On 10/16/11 1:19 PM, "Martin v. Löwis" wrote:
But let me run this by plone-dev, to get some more
feedback/confirmation; I'll get back to you with the exact/complete list.
Please also verify that they are all needed. Minimality is an objective,
so if some plone versions are out-of-date, there is no point in adding a
classifier.
OK Here is the list:
Framework :: Plone :: 3.3
Framework :: Plone :: 4.0
Framework :: Plone :: 4.1
Framework :: Plone :: 4.2
Framework :: Plone :: 4.3
(3.3 was the first Plone version to be distributed as an egg. And 4.3 is
as far in the future as we know about right now.)
To answer the other two questions (I found on the catalog list, sorry, I
guess I should have asked there.)
* what specific semantics would you imply for packages tagged with these
classifiers?
These classifiers imply compatibility with a particular Plone release.
For example, we have add-ons that only work with 4.0 (and not 4.1, etc).
* what specific packages that are already on PyPI would be tagged with
these specific classifiers?
Anyone releasing Plone add-ons to PyPI will now be able to specify
Plone version compatibility in setup.py. I suspect that most, if not
all, actively maintained add-ons will make use of this classifier e.g.
http://pypi.python.org/pypi/Products.PloneFormGen. But there are too
many to list. Note Plone core packages may or may not make use of these
classifiers. They could, but the request is made explicitly on behalf of
add-on developers.
Thank you for considering,
Alex
Regards,
Martin
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
--
Alex Clark · http://aclark.net
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
