From 514294e254ce3a4702e75336e359cc34b2300525 Mon Sep 17 00:00:00 2001 From: Tom Henderson Date: Fri, 3 Jun 2022 14:28:29 -0700 Subject: [PATCH] doc: Update release_steps.txt --- doc/release_steps.txt | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/doc/release_steps.txt b/doc/release_steps.txt index 43b329b62..880f341c4 100644 --- a/doc/release_steps.txt +++ b/doc/release_steps.txt @@ -198,16 +198,12 @@ First, create skeletal sections in CHANGES.html and RELEASE_NOTES.md to start collecting inputs for the ns-3.(x+1) release. The project may decide to make incremental, bug-fix releases from -time to time, with a minor version number (e.g. ns-3.7.1). To do +time to time, with a minor version number (e.g. ns-3.36.1). To do this, changesets may be cherry-picked from ns-3-dev and added to ns-3.x branch. Do not move over changesets that pertain to adding new features, but documentation fixes and bug fixes are good changesets to make available in a minor release. The same steps -above for making a release are generally followed, although one -does not need to create a separate branch, but instead just reopens -the previous release branch, makes the changes, adds a minor version -number as a tag, and merges the branch back with the master branch. - -Also, on the main website, make sure that "latest release" points to -the right page. See how it was handled for ns-3.12 (which made -a minor release): https://www.nsnam.org/ns-3.12/ +above for making a release are generally followed; the documentation +in the manual about working with Git as a maintainer provides the +specific steps to follow. Also, on the main website, make sure that +"latest release" and "latest documentation" points to the right page.