I have now implemented this policy for the trunk and current release
branches of Products.GenericSetup, Products.PluginRegistry and
Products.PluggableAuthService:
- releases and information have their canonical location on PyPI
Done: changed the url metadata in setup.py
- the zope.org
Previously Jens Vagelpohl wrote:
On Jun 11, 2008, at 14:31 , Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
Hi guys,
I'm wondering about the need to provide tarballs for GenericSetup
through zope.org alongside the tarball on PyPI. It's extra work and
the GenericSetup pages on
Hi guys,
I'm wondering about the need to provide tarballs for GenericSetup
through zope.org alongside the tarball on PyPI. It's extra work and
the GenericSetup pages on zope.org don't offer any added value over
its PyPI page.
In order to simplify release management I propose the
Previously Jens Vagelpohl wrote:
Hi guys,
I'm wondering about the need to provide tarballs for GenericSetup
through zope.org alongside the tarball on PyPI. It's extra work and
the GenericSetup pages on zope.org don't offer any added value over
its PyPI page.
We'll keep using tarballs
On Jun 11, 2008, at 14:31 , Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
Hi guys,
I'm wondering about the need to provide tarballs for GenericSetup
through zope.org alongside the tarball on PyPI. It's extra work and
the GenericSetup pages on zope.org don't offer any added value
