libtool/README-alpha

This is an alpha testing release of GNU Libtool.  To get the latest
CVS version of this package, do:

  cvs -d :pserver:anoncvs@subversions.gnu.org:/home/cvs login
  [Hit return when prompted for the password]
  cvs -d :pserver:anoncvs@subversions.gnu.org:/home/cvs checkout libtool
  cd libtool
  ./bootstrap

The `bootstrap' script sets up the source directory for you to hack. To
use it, you need a recent (maybe yet to be released) version of both
Autoconf and Automake.

If you have any suggestions or bug reports, or you wish to port
libtool to a new platform, please send electronic mail to the libtool
mailing list <libtool@gnu.org> or bug reports to <bug-libtool@gnu.org>.
Don't forget to mention the version of libtool that you are currently
using (by typing `libtool --version').

================================================================
= Administrivia

* If you incorporate a change from somebody on the net:
  If it is a large change, you must make sure they have signed the
  appropriate paperwork, and 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.

* 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 libtool package are not owned by libtool.  These
  files should never be edited here.  These files are:
	COPYING
	INSTALL
	config/
	    + config.guess
	    + config.sub
	    + depcomp
	    + install-sh
	    + mdate-sh
	    + missing
	    + texinfo.tex
	doc/
	    + fdl.texi
	libltdl/
	    + COPYING.LESSER
	    + config.guess
	    + config.sub
	    + install-sh
	    + missing

* Changes other than bug fixes must be mentioned in NEWS

================================================================
= Test suite

* Use "make check" liberally, on as many platforms as you can.  Use as
  many compilers and linkers you can.


================================================================
= Release procedure

* If you are a libtool maintainer, but have not yet registered your
  gpg public key and (preferred) email address with the FSF, send an
  email, preferably GPG-signed, to <ftp-upload@gnu.org> that includes
  the following:

    (a) name of package(s) that you are the maintainer for, and your
        preferred email address.

    (b) an ASCII armored copy of your GnuPG key, as an attachment.
	("gpg --export -a YOUR_KEY_ID > mykey.asc" should give you
	this.)

  When you have received acknowledgement of your message, the proper GPG
  keys will be registered on ftp-upload.gnu.org and only then will you be
  authorized to upload files to the FSF ftp machines.

* Update NEWS, ChangeLog.

* Update the version number in configure.ac.
  See http://www.gnu.org/software/libtool/contribute.html for details of
  the numbering scheme.

* Run ./bootstrap.

* Run `make fetch', which will fetch new versions of the files that are
  maintained outside of libtool.

* Run ./configure and then make.

* Run `make cvs-dist' which will build a release tarball (with `make
  distcheck'), commit the last NEWS, ChangeLog and configure.ac changes,
  tag the tree with release-$(VERSION), and generate gpg signature files.

* Run `make cvs-diff' which will create a diff file against the previous
  release tag (set OLDVERSION=min.maj[.mic[alpha]] in the environment
  beforehand if necessary), and generate gpg signature files.

* Make sure you have a copy of xdelta installed, and a copy of the previous
  release tarball in the build directory, then run `make xdelta', which will
  create an xdelta file between this and the previous release tarballs (set
  OLDVERSION=min.maj[.mic[alpha]] in the environment beforehand if necessary),
  and generate gpg signature files.

* Upload release tarball, diff file and xdelta file, plus their associated
  detached gpg signature files and clear signed directive files to
  ftp-upload.gnu.org. If the upload is destined for ftp.gnu.org, then the
  files should be placed in the /incoming/ftp directory.  If the upload is
  an alpha release destined for alpha.gnu.org, then the files should be
  placed in the /incoming/alpha directory.incoming/ftp/gnu/libtool.  Then send
  announcement to libtool@gnu.org and autotools-announce@gnu.org.

* If not an alpha, announcement must also go to info-gnu@gnu.org, and an
  upload request be sent to ftp-upload@gnu.org requesting files be transferred
  from ftp://alpha.gnu.org/gnu/libtool to ftp://ftp.gnu.org/gnu/libtool.

* Update version number in configure.ac to next alpha number.

* Commit.

* Update the front libtool webpage to indicate the latest release
  number, and the news page to reflect the latest release note.

================================================================
= Alpha release note template

To: libtool@gnu.org, autotools-announce@gnu.org

The Libtool Team is pleased to announce alpha release @VERSION@ of GNU
Libtool.

GNU Libtool hides the complexity of using shared libraries behind a
consistent, portable interface. GNU Libtool ships with GNU libltdl,
which hides the complexity of loading dynamic runtime libraries
(modules) behind a consistent, portable interface.

Here are the compressed sources:

  ftp://alpha.gnu.org/gnu/libtool/libtool-@VERSION@.tar.gz
  ftp://alpha.gnu.org/gnu/libtool/libtool-@VERSION@.tar.bz2

Here are the xdeltas and diffs against libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@:

  ftp://alpha.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
  ftp://alpha.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta

Here are the gpg detached signatures:

  ftp://alpha.gnu.org/gnu/libtool/libtool-@VERSION@.tar.gz.sig
  ftp://alpha.gnu.org/gnu/libtool/libtool-@VERSION@.tar.bz2.sig
  ftp://alpha.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz.sig
  ftp://alpha.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta.sig

Here are the MD5 and SHA1 checksums:

  @MD5SUM@ libtool-@VERSION@.tar.gz
  @MD5SUM@ libtool-@VERSION@.tar.bz2
  @MD5SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
  @MD5SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta
  @SHA1SUM@ libtool-@VERSION@.tar.gz
  @SHA1SUM@ libtool-@VERSION@.tar.bz2
  @SHA1SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
  @SHA1SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta

This release has @SUMMARY_OF_IMPROVEMENTS_SINCE_LAST_RELEASE_ON_THIS_BRANCH@.

This release was bootstrapped with @BOOTSTRAP_TOOLS_WITH_VERSIONS@,
but is useable with @COMPATIBLE_AUTOTOOL_VERSIONS@ in your own
projects.

Alternatively, you can fetch the unbootstrapped sourcecode from
anonymous cvs by using the following commands (just hit return when
you are prompted for the password):

  $ cvs -z3 -d :pserver:anoncvs@subversions.gnu.org:/cvsroot/libtool login
  Password:
  $ cvs -z3 -d :pserver:anoncvs@subversions.gnu.org:/cvsroot/libtool \
  co -r @CVS_RELEASE_TAG@ libtool

You will then need to have recent (possibly as yet unreleased) versions
of Automake and Autoconf installed to bootstrap the checked out
sources yourself.

New in @VERSION@: @RELEASE_DATE@

  @EXCERPT_FROM_NEWS_FILE@

Please report bugs to <bug-libtool@gnu.org>.

================================================================
= Full release note template

To: info-gnu@gnu.org
Cc: libtool@gnu.org, autotools-announce@gnu.org

The Libtool Team is pleased to announce the release of GNU Libtool
@VERSION@.

GNU Libtool hides the complexity of using shared libraries behind a
consistent, portable interface. GNU Libtool ships with GNU libltdl,
which hides the comlexity of loading dynamic runtime libraries
(modules) behind a consistent, portable interface.

This release has @SUMMARY_OF_IMPROVEMENTS_SINCE_LAST_RELEASE_ON_THIS_BRANCH@.

New in @VERSION@: @RELEASE_DATE@

  @EXCERPT_FROM_NEWS_FILE@

libtool-@VERSION@ is available now from ftp.gnu.org, along with
diffs and xdeltas against libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@
that are also available from ftp.gnu.org.  Please
use a mirror to reduce stress on the main gnu machine:

  http://www.gnu.org/order/ftp.html

Here are the compressed sources:

  ftp://ftp.gnu.org/gnu/libtool/libtool-@VERSION@.tar.gz
  ftp://ftp.gnu.org/gnu/libtool/libtool-@VERSION@.tar.bz2

Here are the xdeltas and diffs against libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@:

  ftp://ftp.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
  ftp://ftp.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta

Here are the gpg detached signatures:

  ftp://ftp.gnu.org/gnu/libtool/libtool-@VERSION@.tar.gz.sig
  ftp://ftp.gnu.org/gnu/libtool/libtool-@VERSION@.tar.bz2.sig
  ftp://ftp.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz.sig
  ftp://ftp.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta.sig

Here are the MD5 and SHA1 checksums:

  @MD5SUM@ libtool-@VERSION@.tar.gz
  @MD5SUM@ libtool-@VERSION@.tar.bz2
  @MD5SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
  @MD5SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta
  @SHA1SUM@ libtool-@VERSION@.tar.gz
  @SHA1SUM@ libtool-@VERSION@.tar.bz2
  @SHA1SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
  @SHA1SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta

This release was bootstrapped with @BOOTSTRAP_TOOLS_WITH_VERSIONS@,
but is useable with @COMPATIBLE_AUTOTOOL_VERSIONS@ in your own
projects.

Alternatively, you can fetch the unbootstrapped sourcecode from
anonymous cvs by using the following commands (just hit return when
you are prompted for the password):

  $ cvs -z3 -d :pserver:anoncvs@subversions.gnu.org:/cvsroot/libtool login
  Password:
  $ cvs -z3 -d :pserver:anoncvs@subversions.gnu.org:/cvsroot/libtool \
  co -r @CVS_RELEASE_TAG@ libtool

You will then need to have the latest release versions of Automake
(@AUTOMAKE_VERSION@) and Autoconf (@AUTOCONF_VERSION@) installed to
bootstrap the checked out sources yourself.

Please report bugs to <bug-libtool@gnu.org>.