summaryrefslogtreecommitdiff
path: root/RELEASING
blob: afc9f432dd2a3aa51b0ba28ca6617bb4d682ce59 (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
45
46
47
48
49
50
51
52
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 commit
	$ git push origin # make sure you're on the release branch

4. Verify your module builds

	$ make distcheck

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 and send the generated release message.

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

	The message is generated as xf86-video-intel-<version>.announce

	For snapshots and release candidates, mail to:

		intel-gfx@lists.freedesktop.org

	For major releases also send to:

		xorg@lists.freedesktop.org
		xorg-announce@lists.freedesktop.org

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