ref: 92aa527a1ce0f427c5e2446fbe12011b4a307806
dir: /docs/release/
How to prepare a new release ---------------------------- . include/freetype/freetype.h: Update FREETYPE_MAJOR, FREETYPE_MINOR, and FREETYPE_PATCH. . builds/unix/configure.ac (version_info): Update according to the libtool rules, then regenerate the configure script with the top-level `autogen.sh'. After that, update `config.guess' and `config.sub' to the most recent versions (from the `config' CVS repository). . builds/freetype.mk (refdoc): Update the `--title' option. . docs/CHANGES: Document differences to last release. . README: Update. . docs/VERSION.DLL: Document changed `version_info'. . ChangeLog: Announce new release. ********* The items below should be done but are out-of-date due ********* ********* to the move of the FreeType CVS and web pages. ********* . Call `make refdoc' to update HTML reference. Copy it to freetype2/docs/reference in the `www' CVS module and update the CVS. Then call `update-www' in ~/cvs/scripts on www.freetype.org to update and distribute everything to sourceforge. . Tag the CVS (freetype, ft2demos, www/freetype2/docs). . Update `make-release' and `make-current' in ~/cvs/scripts/ on www.freetype.org, then call them. . Create an md5 checksum file (with md5sum). . Announce new release on [email protected] and to relevant newsgroups.