Geoff: could you create a release tarball (and maybe create a document detailed how you generaly do this)
Such a document already exists. It's a little out-of-date (since it's back in the days before SourceForge), but it's still pretty much correct:
http://htdig.org/dev/checklist.html
I'd also add (before tagging the CVS release)
* Check copyright dates in maindocs/ README, and code to ensure they include the current year.
And after adding the tar and diff to the /files directory, you'll also need to:
* Add tar and diff to SF.net release manager
* Add NEWS item to SF.net project page
I think that's pretty much complete.
I'd be glad to help anyone going through the process to make sure there's accurate, up-to-date documentation of what to do. But I *really* think the more people who go through it, the better for the project. If I'm the only one who does it and I'm hit by a bus or fall off the map tomorrow, we're in trouble. :-)
-Geoff
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ht://Dig Developer mailing list: htdig-dev@lists.sourceforge.net List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
