summaryrefslogtreecommitdiff
path: root/Development/Documentation/ReleaseHOWTO.mdwn
diff options
context:
space:
mode:
authorAlanCoopersmith <AlanCoopersmith@web>2013-08-25 15:11:36 -0700
committerxorg <iki-xorg@freedesktop.org>2013-08-25 15:11:36 -0700
commit9f61a0a101edf3ed365a279da333703d47642fe7 (patch)
tree68f67cd58cc75a6a61aacfd9e5241ba208e27dd1 /Development/Documentation/ReleaseHOWTO.mdwn
parent52429cd275adfbecb869881011e984b596cb2312 (diff)
fix formatting after moin->iki conversion
Diffstat (limited to 'Development/Documentation/ReleaseHOWTO.mdwn')
-rw-r--r--Development/Documentation/ReleaseHOWTO.mdwn9
1 files changed, 5 insertions, 4 deletions
diff --git a/Development/Documentation/ReleaseHOWTO.mdwn b/Development/Documentation/ReleaseHOWTO.mdwn
index b14e9a3d..be44cf18 100644
--- a/Development/Documentation/ReleaseHOWTO.mdwn
+++ b/Development/Documentation/ReleaseHOWTO.mdwn
@@ -1,4 +1,3 @@
-
This page is about how to make a module release, for maintainers. If you are wondering about where to download the latest release of X.Org, please see [[XorgReleases|XorgReleases]].
@@ -18,7 +17,8 @@ You **must** make a release if you have changed the ABI or API of your module an
* 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.
-* Commit and push your _version bump_ to the remote repository.
+* Commit and push your _version bump_ to the remote repository.
+
Repeat the above steps for each module you wish to release. The module source from the repository is now ready to be released, meaning the _version bump_ commit is to be tagged, a set of tarballs is to be created and uploaded to the X.Org web site and an announce mail template is to be created which you can send to the xorg-announce mailing list.
The script `util/modular/release.sh` will perform those steps for each module to be released. Invoke the `release.sh` script from any parent directory where the git modules to be released can be reached.
@@ -35,7 +35,8 @@ Where "path" is a relative path to a git module, including '.'.
* The tarballs are uploaded to the X.Org web site in the appropriate section.
* The annotated tag is pushed to the remote repository.
* The announce e-mail template with check-sum is created.
-Consult the help text for the available options. Consider running with `--dry-run` first.
+Consult the help text for the available options. Consider running with `--dry-run` first.
+
## Making katamaris
How to make badged semi-annual rollup releases, for release managers. This is basically what happened for 7.3, only that involved more flailing around.
@@ -51,4 +52,4 @@ How to make badged semi-annual rollup releases, for release managers. This is b
* $EDITOR doc/RELNOTES.txt
* update [[http://wiki.x.org/wiki/Releases/7.x|http://wiki.x.org/wiki/Releases/7.x]]
* update [[http://wiki.x.org/wiki/|http://wiki.x.org/wiki/]] to point to the new release
-* send mail to the list \ No newline at end of file
+* send mail to the list