diff options
author | Paul Smith <psmith@gnu.org> | 2023-02-26 15:52:25 -0500 |
---|---|---|
committer | Paul Smith <psmith@gnu.org> | 2023-02-26 15:52:25 -0500 |
commit | e6bd61d949df4bde73d2f7c09d09df687c9283b2 (patch) | |
tree | 3ab7d480dddf8b9e2022c371e752c66469975455 /README.git | |
parent | fcefae5ec9743c6816fd3bbc896a05526fce9230 (diff) | |
download | make-git-e6bd61d949df4bde73d2f7c09d09df687c9283b2.tar.gz |
* README.git: Clarify some release steps
* README.in: Update some info and remove some obsolete notes.
Diffstat (limited to 'README.git')
-rw-r--r-- | README.git | 13 |
1 files changed, 9 insertions, 4 deletions
@@ -335,10 +335,15 @@ When publishing a final release there are extra steps that need to be taken: Manage the Savannah project for GNU Make: - * In Savannah modify the "Value", "Rank", and "Description" values for the - current "SCM" entry in both "Component Version" and "Fix Release" fields - to refer to the new release. The "Rank" field should be 10 less than the - previous release so it orders properly. + * In Savannah edit the "Component Version" field and choose the "SCM" entry. + Modify the "Value", "Rank", and "Description" values for the to refer to + the new release. The "Rank" field should be 10 less than the previous + release so it orders properly. + + * In Savannah edit the "Fixed Release" field and choose the "SCM" entry. + Modify the "Value", "Rank", and "Description" values for the to refer to + the new release. The "Rank" field should be 10 less than the previous + release so it orders properly. * In Savannah create a new entry for the "Component Version" field: - Value: SCM |