- 5) Verify that the code passes "make distcheck". libdrm is tricky
- to distcheck since the test suite will need to become drm master.
- This means that you need to run it outside X, that is, in text
- mode (KMS or no KMS doesn't matter).
-
- Running "make distcheck" should result in no warnings or errors
- and end with a message of the form:
-
- =============================================
- libdrm-X.Y.Z archives ready for distribution:
- libdrm-X.Y.Z.tar.gz
- libdrm-X.Y.Z.tar.bz2
- =============================================
-
- Make sure that the version number reported by distcheck and in
- the tarball names matches the number you bumped to in configure.ac.
-
- 6) Commit the configure.ac change and make an annotated tag for that
- commit with the version number of the release as the name and a
- message of "libdrm X.Y.Z". For example, for the 2.4.16 release
- the command is:
-
- git tag -a 2.4.16 -m "libdrm 2.4.16"
-
- 7) Push the commit and tag by saying
-
- git push --tags origin master