On Thu, Oct 7, 2010 at 9:40 AM, Nick Burch <nick.bu...@alfresco.com> wrote: > Hi All > > Does anyone happen to know of some pre-existing release guidelines for > python or php libraries, either in an apache TLP or a podling? For Chemistry > we've got the docs sorted for maven-based releases of the java codeline, and > now we're looking to sort something similar for our python and php > codebases. > > Any tips, references and best practices to avoid reinventing the wheel would > be most handy!
For libcloud, we use python's native setup tools to do everything. Things to look at... release.sh: this invokes setup.py to build out source tarballs and then uses the hash/sign script to make the gpg/asc/sha1/md5s: <https://svn.apache.org/repos/asf/incubator/libcloud/tags/0.4.0/dist/release.sh> setup.py: contains lots of metadata about the project, where it is, license, etc: <https://svn.apache.org/repos/asf/incubator/libcloud/tags/0.4.0/setup.py> After a release vote is successful, I've also been uploading the tarballs to PyPi: <http://pypi.python.org/pypi/apache-libcloud> --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
