On 4 March 2010 17:09, Jim Meyering <[email protected]> wrote:
>
> Since I'm hoping to make a release soon,
> it'd be good to document the procedure I will follow.
> The following is what I use for coreutils, gzip, diffutils, idutils,
> parted, cppi and one or two other projects, so I'm hoping it will
> work for grep, too:
To what degree is this automated? It looks from the description as if
you do it manually. I automate most of this in GNU Zile releases. It
would be nice to get a "release" target in gnulib that collates best
practice.
For comparison, here is Zile's make release target:
release: distcheck
agrep -d '^Release' $(VERSION) NEWS | tail -n +3 | head -n -1 >
release-notes && \
git diff --exit-code && \
git tag -a -m "Release tag" rel-`echo $(VERSION) | sed -e 's/\./-/g'`
&& \
git push git.sv.gnu.org:/srv/git/zile.git master && git pull && \
woger gnu,freshmeat $(PACKAGE) "$(PACKAGE_NAME)" $(VERSION) "the tiny
Emacs clone" release-notes && \
rm -f release-notes
(woger is my own release tool, which I can hardly say is
battle-tested, as I know of no other users than myself, but FWIW it's
available from http://rrt.sc3d.org/Software/woger and is of course
GPLed.)
--
http://rrt.sc3d.org
