File: release.txt

package info (click to toggle)
graphite2 1.3.13-7
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 23,300 kB
  • sloc: cpp: 14,690; cs: 1,998; ansic: 1,673; python: 1,481; perl: 184; xml: 123; sh: 96; makefile: 58
file content (48 lines) | stat: -rw-r--r-- 1,753 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
== Release Process ==

These notes are not necessarily part of the manual. They are here for code
developers to remember to do the right thing when it comes to release day.

. `make` and `make docs`
. The first line of the Changelog must be the version number. This is so that
  packagers can extract the version number from the source.
. Make sure the version numbers in the `#defines` reflect the release number in
  `includes/graphite2/Font.h`
. Make sure the libtool version numbers are correct in `src/CMakeLists.txt`
. Test build perl wrapper
. Update `debian-src/changelog` with version of x.y.z-1~palaso1
. Ensure the build.palaso.org gives a clear build for all Graphite targets
  including Linux packages.
. Run the build.palaso.org Graphite Linux Packages - tarball manually. This
  triggers the debian package builds.

=== Distribution locations ===

The release is done by:

. `git tag -s <version>`
. `git archive -o graphite2-<ver>.tgz --prefix=graphite2-<ver>/ <ver>`
. `git archive -o graphite2-minimal-<ver>.tgz --prefix=graphite2-<ver>/ <ve>
   include src LICENSE COPYING README.md`
. `sha1sum graphite2-<ver>.tgz graphite2-minimal-<ver>.tgz >
   graphite2-<ver>.sha1sum`
. Then push up to http://sf.net/projects/silgraphite/files/graphite2 and
  https://github.com/silnrsi/graphite/releases

=== How to do a test pdebuild ===

Here's a sample script to do from the project root directory:
----
mkdir debianbuild
cd debianbuild
cp ../graphite2-x,y.z.tgz graphite_x.y.z.orig.tar.gz
mkdir build
cd build
cp -a ../../debian-src debian
pdebuild
----

== Anticipated API Changes ==

Here are the things we will probably change in the API once we come to the
conclusion that we have got to change the API for some really important reason.