Re: Integration of git-based release workflow into "make dist"

[Ralf Wildenhues]

Hello Roger,

* Roger Leigh wrote on Fri, Aug 14, 2009 at 11:40:18AM CEST:
> 
> An initial implementation follows.  This works, but it does need
> further refinement (error checking, for example).  And probably
> review by a git expert.  I'm sure other people can make it much
> nicer, but this hopefully demonstrates the point.

Thanks.  Not to sound discouraging, but this seems to be able to cope
mostly without any Automake internals (am__remove_distdir is a rather
benign issue) nor need special help from Automake.  That means it can
easily live outside of Automake proper for a while at least, until it
is settled and useful for more than a couple of projects or distros,
as Bob already noted.  You can keep it synchronized across projects
easily by putting the code into a fragment.am file and including that
into your toplevel Makefile.am, and synchronizing the fragment, no?

You could consider submitting this fragment as a gnulib module (where
you just place your code into the Makefile.am part of the modules/..
file.  Or as part of maint.mk, if the gnulib crowd likes that better.

> The distributed release is put on a distribution branch, and its
> parents are both the previous release and the current head.  i.e.
> it's a merge of the old distributed release and the current release.
> This lets you do easy merging of changes between both branches, with
> a correct history.

Nice idea, thanks!

Cheers,
Ralf