ReleaseProcess

From XiphWiki
Revision as of 12:04, 9 May 2009 by Rillian (talk | contribs) (→‎Add new release files: Oops. the previous problem with the checksums was regenerating them all, not clobbering the old ones.)
Jump to navigation Jump to search

Process

Create a release directory under http://svn.xiph.org/releases/

If you are uploading the first release of a project to Xiph.org, then first create a release directory in the svn repository. You can do this using remote svn commands (rather than checking out the entire Xiph.org release archive):

 svn mkdir https://svn.xiph.org/releases/PROJECTNAME

Then check that directory out locally:

 svn co https://svn.xiph.org/releases/PROJECTNAME PROJECTNAME-releases

Add new release files

Add tarballs etc. to your local checkout of the release directory:

 cd PROJECTNAME-releases
 svn add PROJECTNAME-x.x.x.tar.gz

Then, generate MD5 and SHA1 checksums for these files:

 md5sum PROJECTNAME-x.x.x.tar.gz >> MD5SUMS
 sha1sum PROJECTNAME-x.x.x.tar.gz >> SHA1SUMS

Check that the only modifications to the checksums are for the new files:

 svn diff

If everything is ok (and the checksums for other files have not changed), commit:

 svn commit

Update http://www.xiph.org/downloads/

The downloads page is in the normal svn repository for www.xiph.org:

 svn co https://svn.xiph.org/websites/xiph.org/downloads/

Update it with your release tarball name and checksum, and commit.

Mail appropriate lists

Mail your release notes to appropriate project lists. You may also want to send news to:

 Linux Weekly News <lwn@lwn.net>
 comp.os.linux.announce <cola@stump.algebra.com>

Tools

Sebastian Pipping has a script to add tarballs and update the appropriate web pages for libxspf: update.sh. You may want to adapt this for your project.