Hi,
first thanks to Martti for handling the 1.11.5 release!
Now that we have three people who've acted as release manager, and
provided comments on the process, we now have a pretty detailed set of
instructions on how a release is done:
http://cvs.sourceforge.net/viewcvs.py/sofia-sip/sofia-sip/docs/release_management.txt?view=markup
Today I added a few more items to the instructions:
- there's a new "after release" section: the release manager
should now reopen the tree for development by resetting
the version in configure.ac and the RELEASE file (by
doing cp -v RELEASE.template RELEASE)
- I didn't add anything about the darcs tree; I guess the
recommendation would be to tag the darcs tree at the
time a release is made from CVS (i.e. the trees need
not be fully synced); Pekka, any comments?
- I also updated the relnotes.txt template in 'sfnet_www'
module (the website that is)
And then, let's try to remember to update the RELEASE file continuously.
Gathering changes, contributors, etc afterwords is boring work, and much
less painful when done at commit time.
--
under work: Sofia-SIP at http://sofia-sip.sf.net
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
