aboutsummaryrefslogtreecommitdiffstats
path: root/README-maintainer
diff options
context:
space:
mode:
authorJay Berkenbilt <ejb@ql.org>2020-04-06 17:26:47 +0200
committerJay Berkenbilt <ejb@ql.org>2020-04-06 17:26:47 +0200
commit222ec049902e12db8713ff20a1b7ea600b47321b (patch)
tree253f064d3fa837b39d8d0d0db58fae15cae504ec /README-maintainer
parentce6cee357025dfae7276adcc7471a2672649e92a (diff)
downloadqpdf-222ec049902e12db8713ff20a1b7ea600b47321b.tar.zst
Tweak maintainer notes
Diffstat (limited to 'README-maintainer')
-rw-r--r--README-maintainer9
1 files changed, 7 insertions, 2 deletions
diff --git a/README-maintainer b/README-maintainer
index 7919826b..f30f9ad9 100644
--- a/README-maintainer
+++ b/README-maintainer
@@ -102,7 +102,8 @@ RELEASE PREPARATION
* Check for open fuzz crashes at https://oss-fuzz.com
* Check all open issues and pull requests in github and the
- sourceforge trackers. See ~/scripts/github-issues.
+ sourceforge trackers. See ~/scripts/github-issues. Don't forget pull
+ requests.
* Check `TODO` file to make sure all planned items for the release are
done or retargeted.
@@ -160,7 +161,11 @@ RELEASE PREPARATION
* Increment shared library version information as needed (`LT_*` in
`configure.ac`). Remember to rerun ./autogen.sh.
-* Test for performance binary compatibility:
+* Performance test is included with binary compatibility steps. Even
+ if releasing a new major release and not doing binary compatibility
+ testing, do performance testing.
+
+* Test for performance and binary compatibility:
* Check out the last release
* ./configure --enable-werror && make -j$(nproc)
* Check out the current version