mirror of
https://github.com/qpdf/qpdf.git
synced 2024-11-16 01:27:07 +00:00
135 lines
4.7 KiB
Plaintext
135 lines
4.7 KiB
Plaintext
Release Reminders
|
|
=================
|
|
|
|
* Consider running tests with latest gcc and/or valgrind. To do
|
|
this, replace, build with debugging and without shared libraries.
|
|
In build, create z and move each executable into z. Then create a
|
|
script called exec-z that contains:
|
|
|
|
#!/bin/sh
|
|
exec valgrind --suppressions=/tmp/a.supp -q \
|
|
`dirname $0`/z/`basename $0` ${1+"$@"}
|
|
|
|
Symlink exec-v to each executable. /tmp/a.supp can be populated
|
|
with suppressions for libraries, for example:
|
|
|
|
{
|
|
zlib1
|
|
Memcheck:Cond
|
|
fun:inflateReset2
|
|
fun:inflateInit2_
|
|
}
|
|
|
|
You can generate these by running valgrind with --gen-suppressions=yes.
|
|
|
|
* Check all open issues in the sourceforge trackers.
|
|
|
|
* If any interfaces were added or changed, check C API to see whether
|
|
changes are appropriate there as well.
|
|
|
|
* Increment shared library version information as needed
|
|
(libqpdf/build.mk)
|
|
|
|
* Update release notes in manual -- look at diffs and ChangeLog
|
|
|
|
* Add a release entry to ChangeLog
|
|
|
|
* Make sure version numbers are consistent in the following
|
|
locations:
|
|
|
|
configure.ac
|
|
qpdf.spec
|
|
libqpdf/QPDF.cc
|
|
manual/qpdf-manual.xml
|
|
|
|
make_dist verifies this consistency.
|
|
|
|
* Update release date in manual/qpdf-manual.xml
|
|
|
|
* Check TODO file to make sure all planned items for the release are
|
|
done or retargeted.
|
|
|
|
* Each year, update copyright notices. Just search for Copyright.
|
|
Last updated: 2011.
|
|
|
|
* To construct a source distribution from a pristine checkout,
|
|
make_dist does the following:
|
|
|
|
./autogen.sh
|
|
./configure --enable-doc-maintenance --enable-werror
|
|
make build_manual
|
|
make distclean
|
|
|
|
* To create a source release, do an export from the version control
|
|
system to a directory called qpdf-version. For example, from this
|
|
directory:
|
|
|
|
rm -rf /tmp/qpdf-x.y.z
|
|
git archive --prefix=qpdf-x.y.z/ HEAD . | (cd /tmp; tar xf -)
|
|
|
|
From the parent of that directory, run make_dist with the directory
|
|
as an argument. Remember to have fop in your path. For internally
|
|
testing releases, you can run make_dist with the --no-tests option.
|
|
|
|
* To create a source release of external libs, do an export from the
|
|
version control system into a directory called qpdf-external-libs
|
|
and just make a zip file of the result called
|
|
qpdf-external-libs-src.zip. See the README.txt file there for
|
|
information on creating binary external libs releases.
|
|
|
|
* To create Windows binary releases, extract the qpdf source
|
|
distribution in Windows (MSYS + MINGW, MSVC). From the extracted
|
|
directory, extract the binary distribution of the external
|
|
libraries. Run ./make_windows_releases from there. You will need
|
|
to have zip in your path.
|
|
|
|
* Remember to copy README-what-to-download.txt separately onto the
|
|
download area and make it the default for Windows platforms.
|
|
|
|
* Remember to update the web page including putting new documentation
|
|
in the "files" subdirectory of the website on sourceforge.net.
|
|
|
|
* Create a tag in the version control system, and make backups of the
|
|
actual releases. With git, use git tag -s to create a signed tag:
|
|
|
|
git tag -s release-qpdf-$version HEAD -m'qpdf $version'
|
|
|
|
* When releasing on source forge, external-libs distributions go in
|
|
external-libs/yyyymmdd, and qpdf distributions go in qpdf/vvv
|
|
|
|
|
|
General Build Stuff
|
|
===================
|
|
|
|
QPDF uses autoconf and libtool but does not use automake. The only
|
|
files distributed with the qpdf source distribution that are not
|
|
controlled are "configure", "libqpdf/qpdf/qpdf-config.h.in",
|
|
"aclocal.m4", and some documentation. See above for the steps
|
|
required to prepare a source distribution.
|
|
|
|
A small handful of additional files have been taken from autotools
|
|
programs. These should probably be updated from time to time.
|
|
|
|
* config.guess, config.sub, ltmain.sh, and the m4 directory: these
|
|
were created by running libtoolize -c. To update, run libtoolize
|
|
-f -c or remove the files and rerun libtoolize.
|
|
|
|
* Other files copied as indicated:
|
|
|
|
cp /usr/share/automake-1.11/install-sh .
|
|
cp /usr/share/automake-1.11/mkinstalldirs .
|
|
|
|
The entire contents of the m4 directory came from libtool.m4. If we
|
|
had some additional local parts, we could also add those to the m4
|
|
directory. In order for this to work, it is necessary to run "aclocal
|
|
-I m4" before running autoheader and autoconf.
|
|
|
|
If building or editing documentation, configure with
|
|
--enable-doc-maintenance. This will ensure that all tools or files
|
|
required to validate and build documentation are available.
|
|
|
|
If you want to run make maintainer-clean or make distclean and you
|
|
haven't run ./configure, you can pass CLEAN=1 to make on the command
|
|
line to prevent it from complaining about configure not having been
|
|
run.
|