-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathRELEASE
43 lines (23 loc) · 1.18 KB
/
RELEASE
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
Releasing a new version of faf
------------------------------
1. Check that all changes from all work computers are commited. Then
check, that the local clone of the program is up-to-date:
$ git status
$ git pull
2. Check that the version number has been increased after the last
release. If it was not, increase it on the first line of configure.ac.
* configure.ac: Increase version to x.y.
3. Update NEWS file to include user-visible, important informations
about the new release.
* NEWS: Document recent changes.
4. Read and update the README file, if you see that some change made
since the last release expanded the project scope, or added
significant new functionality.
5. Read and update the man pages, to be sure that it's synchronized
with the code.
6. Run ./autogen.sh and the ./configure to update all generated files.
7. Commit all the new changes. Run `make release-minor` or `make release-major`
to make new tag and to create release tarball (faf-x.y.tar.gz).
8. Push the changes to the git server using `git push && git push --tags`.
9. Check contents of the release tarball if every file is in place.
10. Run `make upload` to upload release tarball to the FTP server.