summaryrefslogtreecommitdiff
path: root/RELEASING
blob: ec67224315afaf91f3ae3054bfc21bacd31873ae (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
The process for releasing a new tarball is as follows:

1. Make sure you have the latest build requirements installed:

	git://git.freedesktop.org/git/util/macros
	git://git.freedesktop.org/git/util/modular

2. Add relevant release notes to the NEWS files

	Skim the git log since the last release, and add notes in a
	similar style to previous releases.

	For major releases list added features and known limitations.

	For minor releases indicate which bugs were fixed and which
	are still present.


3. Update your module version (usually found in configure.ac)

	$ vi configure.ac # bump version
        $ git push origin # make sure you're on the release branch

4. Verify your module builds

	$ make distcheck

	Note that unlike a regular "make", this will not work unless
	you pass a valid --with-xserver-source=/path/to/xserver option
	to configure.

5. Tag the release

	$ git tag -m "Intel <ver> release" <ver>

6. Run the release script (this should push the tag)

	$ <path_to>/util/modular/release.sh driver <last_ver> <ver>

7. Edit the generated release message as needed and send it out

	At the very least, add the release notes from the NEWS file.

8. Throw a release party, you're done! :)