summaryrefslogtreecommitdiff
path: root/Development/Documentation/ReleaseHOWTO.mdwn
diff options
context:
space:
mode:
authorKeithPackard <KeithPackard@web>2016-09-16 18:02:15 +0000
committerxorg <iki-xorg@freedesktop.org>2016-09-16 18:02:15 +0000
commitd3630eb335d3d4389e68bdfc44c52c7ed21f7269 (patch)
treec8dd41284a97435af0fea92826ddd3e566aec143 /Development/Documentation/ReleaseHOWTO.mdwn
parent1852096372e09200afaef09d30514c385320ee22 (diff)
Diffstat (limited to 'Development/Documentation/ReleaseHOWTO.mdwn')
-rw-r--r--Development/Documentation/ReleaseHOWTO.mdwn1
1 files changed, 1 insertions, 0 deletions
diff --git a/Development/Documentation/ReleaseHOWTO.mdwn b/Development/Documentation/ReleaseHOWTO.mdwn
index 8cc084ce..f669b6f4 100644
--- a/Development/Documentation/ReleaseHOWTO.mdwn
+++ b/Development/Documentation/ReleaseHOWTO.mdwn
@@ -14,6 +14,7 @@ Make sure you have up-to-date **released** versions of these packages before mak
You **must** make a release if you have changed the ABI or API of your module and other modules rely on it. Likewise, the module to be released must not depend on unreleased code changes in any of its dependencies. Assuming the development and test (including _make distcheck_) have completed successfully and all commits have been pushed to the remote repository, the following steps will perform a _version bump_.
+* Test the build with 'make distcheck' to catch any updates needed to various file/directory lists.
* Pick a suitable version number, according to the [[X.org version number scheme|Development/Documentation/VersionNumberScheme]].
* Apply that version number to configure.ac.
* For the xserver module, update RELEASE_DATE variable as well.