|
|
| (4 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| == Create a release directory under [http://svn.xiph.org/releases/ http://svn.xiph.org/releases/] ==
| | #REDIRECT [[How to do a release]] |
| | |
| 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):
| |
| | |
| <tt>svn mkdir http://svn.xiph.org/releases/PROJECTNAME</tt>
| |
| | |
| Then check that directory out locally:
| |
| | |
| <tt>svn co http://svn.xiph.org/releases/PROJECTNAME PROJECTNAME-releases</tt>
| |
| | |
| == Add new release files ==
| |
| | |
| Add tarballs etc. to your local checkout of the release directory:
| |
| | |
| <tt>cd PROJECTNAME-releases</tt>
| |
| <tt>svn add PROJECTNAME-x.x.x.tar.gz</tt>
| |
| | |
| Then, generate MD5 and SHA1 checksums for these files:
| |
| | |
| <tt>md5sum *.tar.gz > MD5SUMS</tt>
| |
| <tt>sha1sum *.tar.gz > SHA1SUMS</tt>
| |
| | |
| Check that the only modifications to the checksums are for the new files:
| |
| | |
| <tt>svn diff</tt>
| |
| | |
| If everything is ok (and the checksums for other files have not changed), commit:
| |
| | |
| <tt>svn commit</tt>
| |
| | |
| == Mail appropriate lists ==
| |
| | |
| Mail your release notes to appropriate project lists. You may also want to send news to:
| |
| | |
| <tt>Linux Weekly News <lwn@lwn.net></tt>
| |
| <tt>comp.os.linux.announce <cola@stump.algebra.com></tt>
| |