diff options
| author | dbrownell <dbrownell@b42882b7-edfa-0310-969c-e2dbd0fdcd60> | 2009-09-21 18:52:45 +0000 |
|---|---|---|
| committer | dbrownell <dbrownell@b42882b7-edfa-0310-969c-e2dbd0fdcd60> | 2009-09-21 18:52:45 +0000 |
| commit | b11d79110ebea755d139406fa65e484cdc379cf0 (patch) | |
| tree | 227129cd625ef8af7fa5ce934aedc9fdf02814f0 /doc/manual/release.txt | |
| parent | 71af49ca7fb11b0bd0c1ba9578826f49288b68ef (diff) | |
| download | openocd+libswd-b11d79110ebea755d139406fa65e484cdc379cf0.tar.gz openocd+libswd-b11d79110ebea755d139406fa65e484cdc379cf0.tar.bz2 openocd+libswd-b11d79110ebea755d139406fa65e484cdc379cf0.tar.xz openocd+libswd-b11d79110ebea755d139406fa65e484cdc379cf0.zip | |
Remove annoying end-of-line whitespace from doc/* files.
git-svn-id: svn://svn.berlios.de/openocd/trunk@2744 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'doc/manual/release.txt')
| -rw-r--r-- | doc/manual/release.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/manual/release.txt b/doc/manual/release.txt index c7069717..273f228a 100644 --- a/doc/manual/release.txt +++ b/doc/manual/release.txt @@ -113,7 +113,7 @@ tags and incrementing the version. The OpenOCD release process must be carried out on a periodic basis, so the project can realize the benefits presented in answer to the question, -@ref releasewhy. +@ref releasewhy. Starting with the 0.2.0 release, the OpenOCD project should produce a new minor release every month or two, with a major release once a year. @@ -132,7 +132,7 @@ beginning of the development cycle through the delivery of the new release. This section presents guidelines for scheduling key points where the community must be informed of changing conditions. -If T is the time of the next release, then the following schedule +If T is the time of the next release, then the following schedule might describe some of the key milestones of the new release cycle: - T minus one month: start of new development cycle @@ -190,7 +190,7 @@ Even with the release script, some steps require clear user intervention The following steps should be followed to produce each release: -# Produce final patches to the trunk (or release branch): - -# Finalize @c NEWS file to describe the changes in the release + -# Finalize @c NEWS file to describe the changes in the release - This file is Used to automatically post "blurbs" about the project. - This material should be produced during the development cycle. - Add a new item for each @c NEWS-worthy contribution, when committed. @@ -208,7 +208,7 @@ svn cp .../trunk .../branches/${RELEASE_BRANCH} svn cp .../branches/${RELEASE_BRANCH} .../tags/${RELEASE_TAG} @endverbatim - For bug-fix releases produced in their respective branch, a tag - should be created in the repository: + should be created in the repository: @verbatim svn cp .../branches/${RELEASE_BRANCH} .../tags/${RELEASE_TAG} @endverbatim |