Browse Source

Document and automate signature creation for the release archives.

git-svn-id: svn://svn.berlios.de/openocd/trunk@2783 b42882b7-edfa-0310-969c-e2dbd0fdcd60
tags/v0.3.0-rc0
zwelch 12 years ago
parent
commit
7b9f01e0ae
2 changed files with 10 additions and 2 deletions
  1. +2
    -1
      doc/manual/release.txt
  2. +8
    -1
      tools/release.sh

+ 2
- 1
doc/manual/release.txt View File

@@ -224,10 +224,11 @@ svn cp .../branches/${RELEASE_BRANCH} .../tags/${RELEASE_TAG}
-# Produce the package source archives:
-# Start with a clean working copy, used for producing releases only.
-# Switch to release tag branch: svn switch .../${RELEASE_TAG}
-# produce a ChangeLog for the release (using svn2cl).
-# Produce a ChangeLog for the release (using svn2cl).
-# @c bootstrap, @c configure, and @c make the package.
-# Run <code>make distcheck</code> to produce the distribution archives.
-# Run <code>make maintainer-clean</code> verify the repository is empty.
-# Create signature files using md5sum, sha1sum, etc.
-# Publish documentation for the release:
- Allow users to access the documentation for each of our releases.
- Place static copies of the following files on the project website:


+ 8
- 1
tools/release.sh View File

@@ -262,7 +262,14 @@ do_stage() {
echo "Staging package archives:"
mkdir -p archives
for EXT in tar.gz tar.bz2 zip; do
mv -v "${PACKAGE_RELEASE}.${EXT}" archives/
local FILE="${PACKAGE_RELEASE}.${EXT}"
# create archive signatures
for HASH in md5 sha1; do
echo "sign: ${FILE}.${HASH}"
${HASH}sum "${FILE}" > "archives/${FILE}.${HASH}"
done
# save archive
mv -v "${FILE}" archives/
done
cp -a NEWS archives/
cp -a ChangeLog archives/


Loading…
Cancel
Save