How to do a release: Difference between revisions
(Elaborate on what to offer in a release) |
|||
Line 6: | Line 6: | ||
make dist | make dist | ||
Ideally, offer binaries for the different systems. | Ideally, offer binaries for the different systems. This is not required, and many packages (such as libvorbis, etc) ship only as source releases. If in doubt, do what previous releases did. If there are no previous releases, libs usually ship as source only, applications tend to offer binaries. | ||
== Repository check-in == | == Repository check-in == |
Revision as of 08:31, 23 June 2009
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. This is not required, and many packages (such as libvorbis, etc) ship only as source releases. If in doubt, do what previous releases did. If there are no previous releases, libs usually ship as source only, applications tend to offer binaries.
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
- 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.