Re: [PATCH gnumach] Inline version.m4 into configure.ac

From:

Guillem Jover

Subject:

Re: [PATCH gnumach] Inline version.m4 into configure.ac

Date:

Sun, 20 Nov 2011 14:14:16 +0100

User-agent:

Mutt/1.5.21 (2010-09-15)

On Sun, 2011-11-20 at 10:18:42 +0100, Thomas Schwinge wrote:
> How does this work if a new release is to be made? I first have to tag
> the Git tree to get a proper version number, I guess? But it's not too
> much of a problem, as the tag can stay local (and be modified further on,
> if it was tagged wrongly, or there are any last-minute fixes), as long as
> the release is not made public.
Yes, what I do on my projects is:
1. Do any final polish for the release, documentation updates, etc.
2. git tag -s project-M.N.O
3. git clean -Xdf
4. autoreconf -f -i
5. ./configure
6. make distcheck
7. Unpack and make check the release tarball.
8. Install and test.
9. If issues are found, then fix and goto 2 (with -f).
10. git push origin master
11. If push failed due to new commits, rebase or merge and goto 2.
10. git push origin project-M.N.O
11. Upload the tarballs to the release site.
regards,
guillem