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.
Packages needed for releases
Make sure you have up-to-date versions of these packages before making module or katamari releases.
- util/macros
- util/modular
- lib/libxtrans (when building modules such as libX11 or xserver that rely on it)
Making module releases
You must make a release if you have changed the ABI or API of your module and other modules rely on it.
Make sure all relevant changes have been committed to your local repository first with git status -a. Remember, this is git, so git-commit only changes your local repository; you must then do git-push to push your changes out to the world.
- Verify your module builds with make distcheck. Verify that the built module actually works. It shouldn't have any dependencies on unreleased components (e.g. xf86-video-ati shouldn't be released if it depends on changes to xorg-server that are only in git master).
Push your version bump and other changes to the central repository with git-push.
- Tag your release, as foobar-1.2.3, for module foobar version 1.2.3. Note that the tag must have a message ('annotation').
git tag -m "Xorg Server Version 1.0.99.2" xorg-server-1.0.99.2
You can obtain the message used for the previous tag by calling git show xorg-server-1.0.99.2.
- Run the release script from util/modular/release, which will generate an email for you containing the MD5/SHA1 sums of the tarballs, the git log, et al, as well as copying it in place and pushing your tag.
i.e. in your module's directory: <pathto>/util/modular/release.sh proto inputproto-1.4.1 inputproto-1.4.2
- Warning: if you're doing a branch release, the release script will also push what's unpushed on your master branch.
- Update other modules that depend on the change. For the xserver module, change the REQUIRED_MODULES line in configure.ac
There are no more modules remaining in CVS, but if you have to do something there, consult the ancient scrolls.
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.
- on annarchy:
- create /srv/xorg.freedesktop.org/archive/X11R7.x/src
- $EDITOR ~/util/modular/module-list.txt to update the list of modules for this release
- cd /srv/xorg.freedesktop.org/archive/X11R7.x/src
~/util/modular/roll-it-up.sh < ~/util/modular/module-list.txt
- $EDITOR index.html
- mkdir doc
- $EDITOR doc/RELNOTES.txt
update http://wiki.x.org/wiki/ to point to the new release
- send mail to the list