FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

James,

I just make sure my tree is current and do a 'make dist'.  On a real 
release (not a pre release) I tag CVS first and then do the make dist.  
Then I generally untar is somewhere else and build it to make sure I 
haven't left out any files from the EXTRA_DIST lines, and usually I run 
the unittests just to be safe.

For documentation I run db2html on the userguide, tar it up and push that, 
the faq, and the tds protocol files up to the web site.

I'd much rather let someone else do all these crap jobs...er very 
exciting and prestigious open source maintainer functions...and just code, 
but it comes with the territory I guess. ;-)  I'm not terribly good at it 
I'm afraid.

Brian

On Mon, 26 Nov 2001, James Cameron wrote:

> Brian,
> 
> When you do a release, could you document the steps you use in a file in
> CVS?  That way you get peer review of the release process as well.  If
> the same was done for the publishing of the FAQ and Users Guide I'd
> appreciate it.
> 
> (I've just been bitten on the pptp-client project, where I have taken
> over release duties.  How the release packages were built was not
> entered into the CVS tree, so now I have to go and ask prior release
> guy.)