PloneSoftwareCenter, pypi, re-releasing a product

Hi,

I have been wondering about some PloneSoftwareCenter (PSC) stuff,
mostly the pypi additions and its effects on how project owners should
go about releasing a project on plone.org.

In previous versions of PloneSoftwareCenter when you had a final
version 1.2 you could click the re-release transition and the release
would be 1.2.1.  In the Poi project I have not seen that working for a
while: the latest (current) release is still called 1.2 even when I
have released 1.2.6 meanwhile and have clicked re-release each time I
made a new release.  It seems to at least have the effect of letting
Poi show op on top in the http://plone.org/products page.

The 1.2 release page has all 1.2.* releases, which is growing rather long:
http://plone.org/products/poi/releases/1.2

The releases page just lists the main releases, 1.1, 1.2 (both stable)
and 2.0 (experimental, not actually started on that yet):
http://plone.org/products/poi/releases

If I were to create a complete release of each 1.2.* minor release
then this releases page would become unwieldy again.

I guess that is how kupu does it though:
http://plone.org/products/kupu/releases lists 24 releases and I guess
that is readable enough actually.

Hm, then what is the difference between Poi and kupu here?  With Poi I
have set the distutils id in the edit form of the project.  I guess
kupu has not done that.  I am not actually using the distutils part of
PloneSoftwareCenter; I just upload to pypi and (for the 1.2 series) I
manually upload an old-style tarball with just the Poi directory.  So
I guess I might as well remove that distutils setting.


So some questions.

Do we know if the pypi possibilities of PSC are actively used?

What are the equivalants of http://pypi.python.org/simple/ and
http://pypi.python.org/simple/Products.Poi on plone.org?  What link
can be used as index instead of the official pypi?

Are the next two conclusions/recommendations valid?

- Only set the distutils id when you actually use that part of PSC
  (with collective.dist).  Do not use the rerelease transition in this
  case.  And I am not sure if the other transitions (alpha, beta, rc,
  final) make sense then.

- If you do not set the distutils id, the re-release transition works
  fine as it always has.

Cheers,

-- 
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Plone-website mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-website
The Wiki: http://plone.org/development/current/projects/WebsiteTeam