How to do a release: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
You made a new release, the world is waiting for it. | You made a new release, the world is waiting for it. | ||
Here is what to do: | Here is what to do: | ||
== Prepare a tarball == | |||
./autogen.sh | |||
make dist | |||
Ideally, offer binaries for the different systems. | |||
== Repository check-in == | == Repository check-in == | ||
| Line 29: | Line 35: | ||
* [[CodingGuidelines]] | * [[CodingGuidelines]] | ||
* [[MIT approach to design and implementation]] | * [[MIT approach to design and implementation]] | ||
[[Category:Developers stuff]] | |||
Revision as of 23:00, 6 February 2008
You made a new release, the world is waiting for it. Here is what to do:
Prepare a tarball
./autogen.sh make dist
Ideally, offer binaries for the different systems.
Repository check-in
Check-in your release and the updated checksum files MD5SUMS and SHA1SUMS to
https://svn.xiph.org/releases/YOUR-COMPONENT/
Extending the checksum files is easy on a Unix machine:
md5sum YOUR-FILE >> MD5SUMS sha1sum YOUR-FILE >> SHA1SUMS
Website update
After about 30(?) minutes repository changes will be visible on
http://downloads.xiph.org/releases/YOUR-COMPONENT/
Then you should update the download section on the Xiph website. In there repository this file is located at
https://svn.xiph.org/websites/xiph.org/downloads/index.shtml.en
Announcement
Announce your release where apropriate. This can include
- Announce
- Vorbis-Dev (yes, for non-Vorbis releases as well)
- your blog
- the project's FreshMeat page
- <other suitable places>
It might also be a good idea to notify people maintaining ports of your project.