ReleaseProcess - Revision history

Conrad: redirect to How to do a release

2009-06-30T08:28:27Z

redirect to How to do a release

← Older revision		Revision as of 08:28, 30 June 2009
Line 1:		Line 1:
	~~= Process =~~		#REDIRECT [[How to do a release]]

	~~== Create a release directory under~~ [~~http://svn.xiph.org/releases/ 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):~~

	~~<tt>svn mkdir https://svn.xiph.org/releases/PROJECTNAME</tt>~~

	~~Then check that directory out locally:~~

	~~<tt>svn co https://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 PROJECTNAME-x.x.x.tar.gz >> MD5SUMS</tt>~~
	~~<tt>sha1sum PROJECTNAME-x.x.x.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>~~

	~~== Update [http://www.xiph.org/downloads/ http://www.xiph.org/downloads/~~] ==

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

	~~<tt>svn co https://svn.xiph.org/websites/xiph.org/downloads/</tt>~~

	~~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:~~

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

	~~= Tools =~~

	~~Sebastian Pipping has a script to add tarballs and update the appropriate web pages for libxspf:~~
	~~[https://trac.xiph.org/browser/releases/xspf/update.sh update.sh~~]~~. You may want to adapt this for your project.~~

Rillian: /* Add new release files */ Oops. the previous problem with the checksums was regenerating them all, not clobbering the old ones.

2009-05-09T19:04:56Z

Add new release files: Oops. the previous problem with the checksums was regenerating them all, not clobbering the old ones.

← Older revision		Revision as of 19:04, 9 May 2009
Line 20:		Line 20:
	Then, generate MD5 and SHA1 checksums for these files:		Then, generate MD5 and SHA1 checksums for these files:

	<tt>md5sum *.tar.gz >> MD5SUMS</tt>		<tt>md5sum PROJECTNAME-x.x.x.tar.gz >> MD5SUMS</tt>
	<tt>sha1sum *.tar.gz >> SHA1SUMS</tt>		<tt>sha1sum PROJECTNAME-x.x.x.tar.gz >> SHA1SUMS</tt>

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

Rillian: Use https urls to protect the authentication token on commit.

2009-05-09T19:03:41Z

Use https urls to protect the authentication token on commit.

← Older revision		Revision as of 19:03, 9 May 2009
Line 5:		Line 5:
	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):		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>		<tt>svn mkdir https://svn.xiph.org/releases/PROJECTNAME</tt>

	Then check that directory out locally:		Then check that directory out locally:

	<tt>svn co ~~http~~://svn.xiph.org/releases/PROJECTNAME PROJECTNAME-releases</tt>		<tt>svn co https://svn.xiph.org/releases/PROJECTNAME PROJECTNAME-releases</tt>

	== Add new release files ==		== Add new release files ==
Line 35:		Line 35:
	The downloads page is in the normal svn repository for www.xiph.org:		The downloads page is in the normal svn repository for www.xiph.org:

	<tt>svn co ~~http~~://svn.xiph.org/websites/xiph.org/downloads/</tt>		<tt>svn co https://svn.xiph.org/websites/xiph.org/downloads/</tt>

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

Rillian: /* Add new release files */ Don't clobber old checksums when adding new files

2009-05-09T19:01:10Z

Add new release files: Don't clobber old checksums when adding new files

← Older revision		Revision as of 19:01, 9 May 2009
Line 20:		Line 20:
	Then, generate MD5 and SHA1 checksums for these files:		Then, generate MD5 and SHA1 checksums for these files:

	<tt>md5sum *.tar.gz > MD5SUMS</tt>		<tt>md5sum *.tar.gz >> MD5SUMS</tt>
	<tt>sha1sum *.tar.gz > SHA1SUMS</tt>		<tt>sha1sum *.tar.gz >> SHA1SUMS</tt>

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

Conrad: add info on /downloads and update.sh from Sebastian Pipping

2009-05-09T03:44:21Z

add info on /downloads and update.sh from Sebastian Pipping

@@ Line 1: / Line 1: @@
 == Create a release directory under [http://svn.xiph.org/releases/ http://svn.xiph.org/releases/] ==
@@ Line 28: / Line 30: @@
    <tt>svn commit</tt>
 == Mail appropriate lists ==
@@ Line 35: / Line 45: @@
    <tt>Linux Weekly News &lt;lwn@lwn.net&gt;</tt>
    <tt>comp.os.linux.announce &lt;cola@stump.algebra.com&gt;</tt>

Conrad: first cut at documenting release process

2009-05-09T02:25:54Z

first cut at documenting release process

New page

== Create a release directory under [http://svn.xiph.org/releases/ 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):

<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>