File: README.release

package info (click to toggle)
libminc 2.4.03-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 4,268 kB
  • sloc: ansic: 57,089; cpp: 3,654; sh: 100; makefile: 21; ruby: 18
file content (56 lines) | stat: -rw-r--r-- 1,479 bytes parent folder | download | duplicates (2)
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
53
54
55
56

# how to use git and the master and develop branches

http://nvie.com/posts/a-successful-git-branching-model/


# libtool and libraries

We are using libtool to (possibly) generate a shared library
for libminc with a three-component version string.

	CURRENT[:REVISION[:AGE]]


# Release procedure

* Update NEWS from Changelog, add break mark in Changelog

* Update the LIBMINC_SOVERSION in CMakeLists.txt according to the
  following rules:

  0. Each library's version should be updated according to these
     rules INDEPENDENTLY!

  1. If the library source code has changed at all since the last
     update, then increment REVISION (`C:R:A' becomes `C:r+1:A').

  2. If any interfaces have been added, removed, or changed since the
     last update, increment CURRENT, and set REVISION to 0.

  3. If any interfaces have been added since the last public release,
     then increment AGE.

  4. If any interfaces have been removed since the last public release,
     then set AGE to 0.

* ccmake, build, and install.

* Update Documentation (AUTHORS, COPYING, NEWS, README)
   Authors should be sourced from recent commits

* Commit.

* Run CPack to make .tar.gz

* Test build from .tar.gz on another system.

* Copy tar file to distribution site.

* Tag the release branch as "libminc-x-y-z" (MINC x.y.z).

* Update the version number in CMakeLists.txt for the next release in
   order to avoid the problem of multiple releases with the same
   version number

* Commit.