Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 98853 invoked from network); 7 Oct 2010 22:22:53 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Oct 2010 22:22:53 -0000 Received: (qmail 46649 invoked by uid 500); 7 Oct 2010 22:22:52 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 46488 invoked by uid 500); 7 Oct 2010 22:22:52 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 46480 invoked by uid 99); 7 Oct 2010 22:22:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Oct 2010 22:22:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of paul@querna.org designates 209.85.160.47 as permitted sender) Received: from [209.85.160.47] (HELO mail-pw0-f47.google.com) (209.85.160.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Oct 2010 22:22:46 +0000 Received: by pwj1 with SMTP id 1so104787pwj.6 for ; Thu, 07 Oct 2010 15:22:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.14.3 with SMTP id 3mr1188151wfn.399.1286490143610; Thu, 07 Oct 2010 15:22:23 -0700 (PDT) Received: by 10.142.142.5 with HTTP; Thu, 7 Oct 2010 15:22:23 -0700 (PDT) In-Reply-To: References: Date: Thu, 7 Oct 2010 15:22:23 -0700 Message-ID: Subject: Re: Release guidelines for python and php libraries? From: Paul Querna To: general@incubator.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Oct 7, 2010 at 9:40 AM, Nick Burch 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: setup.py: contains lots of metadata about the project, where it is, license, etc: After a release vote is successful, I've also been uploading the tarballs to PyPi: --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org