summaryrefslogtreecommitdiff
path: root/RELEASING
diff options
context:
space:
mode:
authorBehdad Esfahbod <behdad@behdad.org>2008-08-11 15:28:04 -0400
committerBehdad Esfahbod <behdad@behdad.org>2008-08-11 15:28:04 -0400
commit52a8e528694aed3e918398e7d8e2d773eaa04c07 (patch)
treecf54b6aea6b46d138bcf26b0972ad3ed58dc34d4 /RELEASING
parent75acb51a0940916f545f0ffba99ccf7669d0d745 (diff)
[RELEASING] Document how to release with failing tests
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING10
1 files changed, 10 insertions, 0 deletions
diff --git a/RELEASING b/RELEASING
index 13248424..3dfe29bb 100644
--- a/RELEASING
+++ b/RELEASING
@@ -25,6 +25,16 @@ Here are the steps to follow to create a new cairo release:
slim_hidden_def and slim_hidden_proto is needed in the cairo
implementation in the style of other similar calls.
+ In the unfortunate case that you have to push a snapshot out
+ (note, I said snapshot, not release) without the entire test
+ suite passing, here's the magic env vars to set when doing
+ 'make distcheck' and 'make release-publish' that will let you
+ get away with it. At any cost, never ever release without
+ (implied) distchecking. Every time we got around it, it turned
+ out to be a disaster. Anyway, here's the pass code:
+
+ DISPLAY= CAIRO_TEST_TARGET=" "
+
3) Fill out an entry in the NEWS file
Sift through the logs since the last release. This is most