Release-Procedure » History » Revision 3
Revision 2 (stbuehler, 2009-03-26 23:43) → Revision 3/7 (stbuehler, 2009-03-29 11:49)
h1. Prepare bug tracker * Create new "next" version * Move all remaining bugs/features you won't fix to the new version (perhaps disable email notifications in admin settings for this?) h1. Prepare tar balls + checksums + Changes + Downloadlinks See attached file. h1. Release * Tag svn release: <pre>svn @svn copy svn+ssh://svn@svn.lighttpd.net/spawn-fcgi/trunk svn+ssh://svn@svn.lighttpd.net/spawn-fcgi/tags/spawn-fcgi-1.6.xxx -m '- tagged spawn-fcgi 1.6.xxx'</pre> 1.6.xxx'@ * Announce on: ** http://redmine.lighttpd.net/projects/spawn-fcgi/news ** http://blog.lighttpd.net/ (only small notify) ** lighttpd-announce@lists.lighttpd.net ** http://freshmeat.net/projects/spawn-fcgi * Add wiki page Release-1.6.xxx (link it in the redmine version and the wiki frontpage) * Update sources for next version: '- next is 1.6.XXX' ** configure.ac ** CMakeLists.txt ** NEWS