summaryrefslogtreecommitdiff
path: root/RELEASING
blob: 624e8236da21dfdf7eef43247ad417b048dd63d1 (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

The libmbim releases are generated using the GNU autotools.

1) Configure and build the whole project, making sure gtk-doc is enabled:

    $ NOCONFIGURE=1 ./autogen.sh
    $ ./configure --enable-gtk-doc
    $ make -j8

2) Run distcheck so that the source distribution tarball is generated, and the
   project test suite is run on it:

    $ make distcheck

3) Compute checksum of the tarball so that it can be referenced in the release
   email:

    $ sha256sum libmbim-${VERSION}.tar.xz

4) Sign release tarball, and verify it (*):

    $ gpg --detach-sign --armor libmbim-${VERSION}.tar.xz
    $ gpg --verify libmbim-${VERSION}.tar.xz.asc libmbim-${VERSION}.tar.xz

5) Upload source tarball (.tar.xz) and signature (.tar.xz.asc) to
   freedesktop.org

TODO: manpages and gtk-doc references

-------------------------------------------------------------------------------

*) Verifying the release signature requires the public key of the person who
   signed it, e.g.:

    $ curl https://www.freedesktop.org/software/libmbim/0x3CAD53398973FFFA.asc | gpg --import