Integration of git release workflow with automake "make dist"

[I'm not subscribed to the list, so I'd appreciate a CC on reply, thanks!]

Hi folks,

After initially bringing up the idea behind this initial implementation
on the automake mailing list, I want to get some criticism and comments
from automake users who use git (or git experts in general in case my
use of the git plumbing is not correct!).

The initial discussion is here:
http://thread.gmane.org/gmane.comp.sysutils.automake.general/10936

And the current implementation is attached.


Automake has a "dist" target to generate a "release" in the form of a
compressed tarfile or zip file.  This file contains files not normally
kept under version control in the developer's repo (generated autotools
scripts, other generated files such as changelogs etc.) as well as
possibly excluding other bits in the repo not needed by end users.
However, this isn't kept under version control, and it would be
helpful it it was.

The above thread contains most of the rationale behind doing this, so
I won't repeat it all here.

The attached make fragment implements a "dist-git" target.  Instead
of releasing by creating a tarball, it injects the same tree onto a
specified git branch and (optionally) signs both the release and
distribution branches.  Branch and tag names and messages are
configurable.  Note this is just an initial proof of concept;
anything can be changed!

I'd like to make this as generally usable for as many people as
possible, so it would be great to hear how you are managing releases
with automake and git, and if this would be useful for you, and if
there's anything that could be added or changed to better accommodate
you.


Many thanks,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.