Release-Procedure » History » Revision 5
Revision 4 (stbuehler, 2012-08-11 10:42) → Revision 5/7 (stbuehler, 2019-08-20 15:07)
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 git commit: svn release: <pre>git tag -s <pre>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 'spawn-fcgi '- tagged spawn-fcgi 1.6.xxx'</pre> * 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