summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2020-07-17 09:30:49 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2020-07-17 09:30:49 +0200
commita809dd02ecba76d0a9f5ed3d3a21c96e0c3eae96 (patch)
treeb7c140fcc3fef5c1022469dcccf4a0980707d7ba
parent273153c2e9a3a67c1853abb9c7a85ef6f778e3ac (diff)
Update release documentation
-rw-r--r--doc/release.cli10
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/release.cli b/doc/release.cli
index 6def002..eecd155 100644
--- a/doc/release.cli
+++ b/doc/release.cli
@@ -44,6 +44,10 @@ distribution from \c{etc/stage} and add the pre-distributed packages
Use the \c{git/copyright} script. See the script header for instructions.
+ Note that most of (all?) our project have been converted to the automatic
+ copyright update notification via a pre-commit hook. So perhaps this step
+ can be removed.
+
\h#etc|Update \c{etc/git/modules}|
Review for any new modules. Remove \c{etc/} and \c{private/} from
@@ -81,7 +85,8 @@ distribution from \c{etc/stage} and add the pre-distributed packages
\h#packaging|Release \c{packaging/} dependencies|
Release dependencies that have the snapshot version as described in
- \c{private/build2-packaging.txt}.
+ \l{https://github.com/build2-packaging/README#version-and-release-management
+ Version and Release Management}.
\N|Maybe this should be done during queuing? Why do we release (but not
publish) these now and other dependencies later? Maybe so that we can
@@ -193,6 +198,9 @@ distribution from \c{etc/stage} and add the pre-distributed packages
\h#stage-machines|Update \c{stage} \c{buildtab}s and build machines|
+ Note: normally, we try to do all of this as part of normal development
+ (e.g., when adding new machines, etc).
+
Review \c{stage} \c{buildtab} for any configurations to drop (for example,
an intermediate version of a compiler), classes to adjust (\c{legacy},
\c{default}, \c{latest}, etc).