| 1 |
Here are the steps to follow to create a new libgxps release: |
| 2 |
|
| 3 |
1) Ensure that there are no local, uncommitted modifications. |
| 4 |
It's probably good enough if "git diff HEAD" doesn't output |
| 5 |
anything and your "master" and "origin" branchs are at the current |
| 6 |
revision. |
| 7 |
|
| 8 |
2) Fill out an entry in the NEWS file |
| 9 |
|
| 10 |
Sift through the logs since the last release. This is most |
| 11 |
easily done with a comand such as: |
| 12 |
|
| 13 |
git log --stat X.Y.Z.. |
| 14 |
|
| 15 |
where X.Y.Z is the previous release version. |
| 16 |
|
| 17 |
Summarize major changes briefly in a style similar to other |
| 18 |
entries in NEWS. Take special care to note any additions in |
| 19 |
the API. These should be easy to find by noting modifications |
| 20 |
to .h files in the log command above. And more specifically, |
| 21 |
the following command will show each patch that has changed a |
| 22 |
public header file since the given version: |
| 23 |
|
| 24 |
find libgxps -name 'gxps*.h' ! -name '*-private.h' \ |
| 25 |
! -name 'gxps-archive.h' ! -name 'gxps-debug.h' \ |
| 26 |
! -name 'gxps-fonts.h' ! -name 'gxps-images.h' \ |
| 27 |
! -name 'gxps-brush.h' ! -name 'gxps-color.h' \ |
| 28 |
! -name 'gxps-path.h' ! -name 'gxps-glyphs.h' \ |
| 29 |
! -name 'gxps-matrix.h' \ |
| 30 |
! -name 'gxps-parse-utils.h' | xargs git log -p X.Y.Z.. -- |
| 31 |
|
| 32 |
3) Increment the gxps version in meson.build: |
| 33 |
|
| 34 |
If there are API additions, then increment the minor version |
| 35 |
and reset the micro version to 0. |
| 36 |
|
| 37 |
Otherwise, (ie. there are only bug fixes), increment |
| 38 |
the micro version to the next larger number. |
| 39 |
|
| 40 |
Adjust current, revision and age as described in the |
| 41 |
comments in the top level meson.build. |
| 42 |
|
| 43 |
5) Commit the changes to NEWS and meson.build |
| 44 |
|
| 45 |
It's especially important to mention the new version number in your |
| 46 |
commit log. |
| 47 |
|
| 48 |
6) Run "ninja libgxps-doc release" |
| 49 |
|
| 50 |
Running "ninja libgxps-doc release" generates the new tarball on the form of: |
| 51 |
|
| 52 |
libgxps-X.Y.Z.tar.xz |
| 53 |
|
| 54 |
(But the tar file isn't actually ready yet, as we still have |
| 55 |
some more steps to follow). |
| 56 |
|
| 57 |
7) Push the commit |
| 58 |
|
| 59 |
8) Tag the release with the following command: |
| 60 |
|
| 61 |
git tag -s -m "libgxps X.Y.Z release" X.Y.Z |
| 62 |
|
| 63 |
9) Push the newly created tag out to the central tree with a command |
| 64 |
something like: |
| 65 |
|
| 66 |
git push origin X.Y.Z |
| 67 |
|
| 68 |
10) Upload the tarball to ftp.gnome.org, by scp-ing it to |
| 69 |
master.gnome.org: |
| 70 |
|
| 71 |
scp libgxps-X.Y.Z.tar.xz (username)@master.gnome.org: |
| 72 |
|
| 73 |
11) ssh into master.gnome.org and call ftpadmin install command: |
| 74 |
|
| 75 |
ftpadmin install libgxps-X.Y.Z.tar.xz |
| 76 |
|
| 77 |
12) Send a message to announce the new release to [email protected] |
| 78 |
|