2003-01-15 Havoc Pennington <hp@redhat.com>

	* dbus/dbus-test.c (dbus_internal_symbol_do_not_use_run_tests):
	fix build when --disable-tests

	* Makefile.am (EXTRA_DIST): put HACKING in here

	* HACKING: document procedure for making a tarball release.

1 files changed, 33 insertions, 0 deletions

diff --git a/HACKING b/HACKING
index 8d0b1756..ed76b3af 100644
--- a/HACKING
+++ b/HACKING
@@ -59,4 +59,37 @@ Coding Style
    data). Avoiding heuristics is also important for security reasons;
    if it looks funny, ignore it (or exit, or disconnect).
 
+Making a release
+===
+
+To make a release of D-BUS, do the following:
+
+ - check out a fresh copy from CVS
+
+ - increment the version number in configure.in
+
+ - verify that the libtool versioning/library soname is 
+   changed if it needs to be, or not changed if not
+
+ - update the file NEWS based on the ChangeLog
+
+ - "make distcheck" (DO NOT just "make dist" - pass the check!)
+
+ - if make distcheck fails, fix it.
+
+ - once distcheck succeeds, "cvs commit"
+
+ - if someone else made changes and the commit fails, 
+   you have to "cvs up" and run "make distcheck" again
+
+ - once the commit succeeds, "cvs tag DBUS_X_Y_Z" where 
+   X_Y_Z map to version X.Y.Z
+
+ - check out the "web" module, copy the tarball to 
+   web/content/software/dbus/releases, "cvs add -kb dbus-x.y.z.tar.gz"
+
+ - update web/content/software/dbus/main.in with a pointer to the 
+   tarball
+  
+ - post to message-bus-list@freedesktop.org announcing the release.