|
|
|
|
@ -1,26 +1,26 @@ |
|
|
|
|
How to prepare a new release |
|
|
|
|
---------------------------- |
|
|
|
|
|
|
|
|
|
. include/freetype/freetype.h: Update FREETYPE_MAJOR, FREETYPE_MINOR, |
|
|
|
|
and FREETYPE_PATCH. |
|
|
|
|
. include/freetype/freetype.h: Update `FREETYPE_MAJOR`, |
|
|
|
|
`FREETYPE_MINOR`, and `FREETYPE_PATCH`. |
|
|
|
|
|
|
|
|
|
. Update version numbers in all files where necessary (for example, do |
|
|
|
|
a grep for both `2.3.1' and `231' for release 2.3.1). |
|
|
|
|
a grep for both '2.10.4' and '2104' for release 2.10.4). |
|
|
|
|
|
|
|
|
|
. builds/unix/configure.raw: Update `version_info'. |
|
|
|
|
. builds/unix/configure.raw: Update `version_info`. |
|
|
|
|
|
|
|
|
|
. docs/CHANGES: Document differences to last release. |
|
|
|
|
|
|
|
|
|
. README: Update. |
|
|
|
|
|
|
|
|
|
. docs/VERSIONS.TXT: Document changed `version_info'. |
|
|
|
|
. docs/VERSIONS.TXT: Document changed `version_info`. |
|
|
|
|
|
|
|
|
|
. ChangeLog: Announce new release (both in the freetype2 and |
|
|
|
|
freetype2-demos modules). |
|
|
|
|
. ChangeLog: Announce new release (both in the 'freetype' and |
|
|
|
|
'freetype-demos' repositories). |
|
|
|
|
|
|
|
|
|
. Clone the git archive to another directory with |
|
|
|
|
|
|
|
|
|
git clone -l -s . ../freetype2.test |
|
|
|
|
git clone -l -s . ../freetype.test |
|
|
|
|
|
|
|
|
|
or something like this and run |
|
|
|
|
|
|
|
|
|
@ -35,14 +35,14 @@ How to prepare a new release |
|
|
|
|
|
|
|
|
|
in the cloned repository to test compilation with both gcc and g++. |
|
|
|
|
|
|
|
|
|
. Test C++ compilation for freetype2-demos too (using `git clone' as |
|
|
|
|
. Test C++ compilation for 'freetype-demos' too (using `git clone` as |
|
|
|
|
above). |
|
|
|
|
|
|
|
|
|
. Run src/tools/chktrcmp.py and check that there are no undefined |
|
|
|
|
trace_XXXX macros. |
|
|
|
|
. Run `src/tools/chktrcmp.py` and check that there are no undefined |
|
|
|
|
`trace_XXXX` macros. |
|
|
|
|
|
|
|
|
|
. After pushing the new release, tag the git repositories (freetype2, |
|
|
|
|
freetype2-demos) with |
|
|
|
|
. After pushing the new release, tag the git repositories ('freetype', |
|
|
|
|
'freetype-demos') with |
|
|
|
|
|
|
|
|
|
git tag VER-<version> -m "" -u <committer> |
|
|
|
|
|
|
|
|
|
@ -54,29 +54,29 @@ How to prepare a new release |
|
|
|
|
|
|
|
|
|
git clean -ndx |
|
|
|
|
|
|
|
|
|
that the git directory is really clean (and remove extraneous files |
|
|
|
|
that the git directory is really clean (and remove extraneous files |
|
|
|
|
if necessary). |
|
|
|
|
|
|
|
|
|
. Say `make dist' in both the freetype2 and freetype2-demos modules |
|
|
|
|
to generate the .tar.gz, .tar.xz, and .zip files. |
|
|
|
|
. Say `make dist` in both the 'freetype' and 'freetype-demos' |
|
|
|
|
repositories to generate the `.tar.gz`, `.tar.xz`, and `.zip` files. |
|
|
|
|
|
|
|
|
|
. Create the doc bundles (freetype-doc-<version>.tar.gz, |
|
|
|
|
freetype-doc-<version>.tar.xz, ftdoc<version>.zip). This is |
|
|
|
|
. Create the doc bundles (`freetype-doc-<version>.tar.gz`, |
|
|
|
|
`freetype-doc-<version>.tar.xz`, `ftdoc<version>.zip`). This is |
|
|
|
|
everything in |
|
|
|
|
|
|
|
|
|
<freetype-web git repository>/freetype2/docs |
|
|
|
|
|
|
|
|
|
except the `reference' subdirectory. Do *not* use option `-l' from |
|
|
|
|
except the `reference` subdirectory. Do *not* use option `-l` from |
|
|
|
|
zip! |
|
|
|
|
|
|
|
|
|
. Run the following script (with updated `$VERSION', `$SAVANNAH_USER', |
|
|
|
|
and $SOURCEFORGE_USER variables) to sign and upload the bundles to |
|
|
|
|
. Run the following script (with updated `$VERSION`, `$SAVANNAH_USER`, |
|
|
|
|
and `$SOURCEFORGE_USER` variables) to sign and upload the bundles to |
|
|
|
|
both Savannah and SourceForge. The signing code has been taken from |
|
|
|
|
the `gnupload' script (part of the automake bundle). |
|
|
|
|
the `gnupload` script (part of the 'automake' bundle). |
|
|
|
|
|
|
|
|
|
#!/bin/sh |
|
|
|
|
|
|
|
|
|
VERSION=2.5.1 |
|
|
|
|
VERSION=2.10.4 |
|
|
|
|
SAVANNAH_USER=wl |
|
|
|
|
SOURCEFORGE_USER=wlemb |
|
|
|
|
|
|
|
|
|
@ -155,12 +155,13 @@ How to prepare a new release |
|
|
|
|
|
|
|
|
|
# EOF |
|
|
|
|
|
|
|
|
|
. Prepare a README for SourceForge and upload it with the following |
|
|
|
|
script (with updated `$VERSION' and $SOURCEFORGE_USER variables). |
|
|
|
|
. Prepare a `README` file for SourceForge and upload it with the |
|
|
|
|
following script (with updated `$VERSION` and `$SOURCEFORGE_USER` |
|
|
|
|
variables). |
|
|
|
|
|
|
|
|
|
#!/bin/sh |
|
|
|
|
|
|
|
|
|
VERSION=2.5.1 |
|
|
|
|
VERSION=2.10.4 |
|
|
|
|
SOURCEFORGE_USER=wlemb |
|
|
|
|
|
|
|
|
|
##################################################################### |
|
|
|
|
@ -170,22 +171,22 @@ How to prepare a new release |
|
|
|
|
|
|
|
|
|
# EOF |
|
|
|
|
|
|
|
|
|
. On SourceForge, tag the just uploaded `ftXXX.zip' and |
|
|
|
|
`freetype-XXX.tar.xz' files as the default files to download for |
|
|
|
|
`Windows' and `Others', respectively. |
|
|
|
|
. On SourceForge, tag the just uploaded `ftXXX.zip` and |
|
|
|
|
`freetype-XXX.tar.xz` files as the default files to download for |
|
|
|
|
'Windows' and 'Others', respectively. |
|
|
|
|
|
|
|
|
|
. Copy the reference files (generated by `make dist') to |
|
|
|
|
. Copy the reference files (generated by `make dist`) to |
|
|
|
|
|
|
|
|
|
<freetype-web git repository>/freetype2/docs/reference |
|
|
|
|
|
|
|
|
|
. Update the `freetype-web' repository. `git push' then automatically |
|
|
|
|
triggers an update of the public web pages within ten minutes, due |
|
|
|
|
to a cron script (on wl@freedesktop.org) that rsyncs with |
|
|
|
|
. Update the 'freetype-web' repository. `git push` then automatically |
|
|
|
|
triggers an update of the public web pages within ten minutes due to |
|
|
|
|
a cron script (on 'wl@freedesktop.org') that rsyncs with |
|
|
|
|
|
|
|
|
|
freedesktop.org://srv/freetype.freedesktop.org/www |
|
|
|
|
|
|
|
|
|
. Announce new release on freetype-announce@nongnu.org and to relevant |
|
|
|
|
newsgroups. |
|
|
|
|
. Announce new release on 'freetype-announce@nongnu.org' and to |
|
|
|
|
relevant newsgroups. |
|
|
|
|
|
|
|
|
|
---------------------------------------------------------------------- |
|
|
|
|
|
|
|
|
|
|
Werner Lemberg
4 years ago