aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorDavid Brownell <dbrownell@users.sourceforge.net>2009-11-04 16:46:27 -0800
committerDavid Brownell <dbrownell@users.sourceforge.net>2009-11-04 16:46:27 -0800
commit16f485aca2193b06d182ab30dd5afe36826e92b5 (patch)
tree3465f2a83b06a29f88ead79a9733c7b8e6ed0482 /doc
parent0e37ea6499fd493a32ebdfd3a27c6a01426b3a19 (diff)
Other files: stop referring to ChangeLog too
The ChangeLog idiom is redundant given any decent SCM. Time to phase it out here. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'doc')
-rw-r--r--doc/manual/release.txt4
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/manual/release.txt b/doc/manual/release.txt
index 31bf44d4..d05ac74d 100644
--- a/doc/manual/release.txt
+++ b/doc/manual/release.txt
@@ -311,7 +311,6 @@ git tag -m "The openocd-${PACKAGE_VERSION} release." "${PACKAGE_TAG}"
release's tag. This is used only for producing these packages.
-# Checkout the appropriate tag:
<code>git checkout "${PACKAGE_VERSION}"</code>
- -# Produce a ChangeLog for the release (using @c git2cl).
-# @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.
@@ -320,7 +319,6 @@ git tag -m "The openocd-${PACKAGE_VERSION} release." "${PACKAGE_TAG}"
- Allow users to access the documentation for each of our releases.
- Place static copies of the following files on the project website:
- @c NEWS: to provide a blurb for each release
- - @c ChangeLog: to show exactly what has been changed
- User's Guide, Developer Manual: to allow easy on-line viewing
-# Upload packages and post announcements of their availability:
-# Release packages into files section of project sites:
@@ -334,7 +332,7 @@ git tag -m "The openocd-${PACKAGE_VERSION} release." "${PACKAGE_TAG}"
- .zip: Windows
- Berlios:
-# Create the new release for the new version.
- -# Provide @c NEWS and ChangeLog files, as requested.
+ -# Provide @c NEWS file, as requested.
-# Upload files via FTP to ftp://ftp.berlios.de/incoming/
-# Edit descriptions for each file.
-# Click button to send E-mail Release Notice.