Finally got around to finishing and releasing the egg for generating content / plone sites matching different profiles - e.g. intranet, public etc.
http://pypi.python.org/pypi/collective.contentgenerator ... our second cheeseshop / plone.org release and the first that I acted as release manager for.
Technical gotchas regarding releasing code
Do all your metadata in the right places first then use setup tools to regenerate the metadata files.
So my recommendation is start at the top with setup.cfg which should release tag changed from dev to nothing and svn from true to false ... or else you get _rSVNnumber appended to your release versions.
Next setup.py add your metadata here (classifiers can be found on the pypi form dropdown) ... then make sure the version you specify in setup.py is copied to the one in egg.name/version.txt
Next get your final text ready in README.txt and HISTORY.txt (using restructured text)
> python2.4 setup.py egg_info
this regenerates your.eggname.egg-info/PKG-INFO and the other metadata files. So you can check them before uploading.
Finally you cpuld upload PKG-INFO to pypi by hand but is easier to do it all in one fell swoop via setuptools register.
> python2.4 setup.py register sdist bdist_egg upload
(the sdist makes a source tarball and the bdist_egg and egg)
If you really need to do final tweakings ... via the pypi web form ... you can do so but you will then have to go to the generated PKG_INFO link on pypi and copy and paste the results back into README.txt etc., rerun egg-info and re-upload your egg tarball ... I did all that at first and then realised that was a really bad idea!
Lastly all you need to do is go through the whole process again via different web forms on plone.org ;-)
... though I think this is being addressed?
* Oh and one final bugbear ... where do you set platform in the metadata?