-
Notifications
You must be signed in to change notification settings - Fork 22
/
RELEASE
30 lines (19 loc) · 954 Bytes
/
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
Releasing a new version of satyr
--------------------------------
1. Check that all changes from all work computers are committed. Then
check, that the local clone of the program is up-to-date:
$ git status
$ git pull
2. In lib/Makefile.am, update the library version according to the libtool documentation
(info(1) libtool or https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html):
libsatyr_la_LDFLAGS = -version-info 2:1:0
3. Update NEWS file to include user-visible, important informations
about the new release. Provide the date of the release (Released
YYYY-MM-DD).
* NEWS: Document recent changes.
4. Read and update the README.md 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 page, to be sure that it's synchronized
with the code.
6. Run make release-{minor,major}, when all changes are committed.