From: Gary V. Vaughan <gary@gnu.org>
Date: Tue, 8 Dec 1998 18:36:31 +0000 (+0000)
Subject: new release procedure
X-Git-Tag: release-1-2d~22
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7bb6cc50a7830d45039dd87159c013b1ab31e91c;p=thirdparty%2Flibtool.git

new release procedure
---

diff --git a/ChangeLog b/ChangeLog
index 573fbdaa0..bf3a987b5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,12 @@
+1998-12-08  Gary V. Vaughan  <gvaughan@oranda.demon.co.uk>
+
+	* README-alpha: adapted the release procedure from
+	  automake/HACKING.
+	* Makefile.am: adapted the cvs-dist and cvs-diff rules from
+	  automake/Makefile.am.  I guess this is probably safe to use
+	  already, but I didn't test it as it tags the CVS tree.  If
+	  it needs tweaking, we'll find out come 1.2d.
+
 1998-12-08  Thomas Tanner  <tanner@gmx.de>
 
 	* ltconfig.in: fixed some typos in archive_sym_cmds
diff --git a/Makefile.am b/Makefile.am
index 3bf785b32..cb29286ab 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -153,3 +153,28 @@ $(srcdir)/libltdl/configure: libltdl/configure.in libltdl/aclocal.m4
 
 $(srcdir)/libltdl/aclocal.m4: libltdl/configure.in libltdl/acinclude.m4
 	cd $(srcdir)/libltdl && $(ACLOCAL)
+
+################################################################
+##
+## Everything past here is useful to the maintainer, but probably not
+## to anybody else (snarfed from automake/Makefile.am).
+##
+
+# Tag before making distribution.  Also, don't make a distribution if
+# checks fail.  Also, make sure the NEWS file is up-to-date.
+cvs-dist: distcheck
+	@if sed 1q $(srcdir)/NEWS | grep -e "$(VERSION)" > /dev/null; then :; else \
+	  echo "NEWS not updated; not releasing" 1>&2; \
+	  exit 1;				\
+	fi
+	cd $(srcdir) && cvs -q tag `echo "Release-$(VERSION)" | sed 's/\./-/g'`
+	$(MAKE) dist
+
+cvs-diff:
+	thisver=`echo "Release-$(VERSION)" | sed 's/\./-/g'`; \
+	if test -z "$$OLDVERSION"; then \
+	  prevno=`echo "$(VERSION)" - 0.01 | bc | sed 's/^\./0./'`; \
+	else prevno="$$OLDVERSION"; fi; \
+	prevver=Release-`echo $$prevno | sed 's/\./-/g'`; \
+	cvs -f rdiff -c -r $$prevver -r $$thisver $(PACKAGE) \
+	    > $(PACKAGE)-$$prevno-$(VERSION).diff
diff --git a/README-alpha b/README-alpha
index 6508b539e..1b41fb65e 100644
--- a/README-alpha
+++ b/README-alpha
@@ -13,3 +13,61 @@ use it, you need a recent version of both Autoconf and Automake.
 Please do not send any bug reports or questions about this snapshot to
 public forums (such as GNU newsgroups), send them directly to the
 libtool mailing list, <bug-libtool@gnu.org>.
+
+================================================================
+= Administrivia
+
+* If you incorporate a change from somebody on the net:
+  First, if it is a large change, you must make sure they have signed the
+  appropriate paperwork.
+  Second, be sure to add their name and email address to THANKS
+
+* If a change fixes a test, mention the test in the ChangeLog entry.
+
+* If somebody reports a new bug, mention his name in the ChangeLog entry
+  and in the test case you write.  Put him into THANKS.
+
+* The correct response to most actual bugs is to write a new test case
+  which demonstrates the bug.  Then fix the bug, re-run the test suite,
+  and check everything in.
+
+* Some files in the automake package are not owned by libtool.  These
+  files should never be edited here.  These files are COPYING, INSTALL,
+  config.guess config.sub, install-sh, mdate-sh, mkinstalldirs, texinfo.tex
+
+* Changes other than bug fixes must be mentioned in NEWS
+
+================================================================
+= Test suite
+
+* Use "make check" and "make maintainer-check" liberally
+
+* Make sure each test file is executable
+
+
+================================================================
+= Release procedure
+
+* Fetch new versions of the files that are maintained by the FSF.
+  Commit.  Unfortunately you need an FSF account to do this.
+
+* Update NEWS.  For an alpha release, update README-alpha.
+
+* Update the version number in configure.in.
+  (The idea is that every other alpha number will be a net release.
+  The repository will always have its own "odd" number so we can easily
+  distinguish net and repo versions.)
+
+* Configure, build, and install.
+
+* Run aclocal, automake, and autoconf.
+
+* Commit
+
+* Run `make cvs-dist'
+
+* Put new release on ftp site and send announcement.
+  (If not an alpha, announcement must also go to FSF.)
+
+* Update version number in configure.in to next alpha number.
+  Re-run autoconf and commit.