Commit 94242a12 authored by Kai Vehmanen's avatar Kai Vehmanen

Updated developer docs w.r.t. VCS system. Darcs is now the primary version...

Updated developer docs w.r.t. VCS system. Darcs is now the primary version control system and sf.net CVS is only used as a backup.

darcs-hash:20060504154417-7659e-e416b6828f4b90ef29a9be400de5f32442cea53a.gz
parent 3e10ea6d
......@@ -44,7 +44,7 @@ For development releases and snaphots the version is one of:
vMAJOR.MINOR.REVISION.YEAR.MONTH.DAY, where minor is odd
For all releases, the version should be changed in configure.ac
and committed to CVS before making the release package. The person
and committed to Darcs/CVS before making the release package. The person
doing the release is responsible for updating the version number.
......@@ -57,10 +57,14 @@ TBD
Version control tags
====================
Tags at sourceforge.net CVS
---------------------------
Tagging releases and snapshots
------------------------------
- server info: http://sourceforge.net/cvs/?group_id=143636
- source repository (*)
- master Darcs tree at:
http://dev-126.openlaboratory.net/repos/sofia-sip
- CVS tree (only used to track major releases) at:
http://sourceforge.net/cvs/?group_id=143636
- tags: rel-sofia-sip-x_y_z
- stable and development releases (matches release
version sofia-sip-x.y.z)
......@@ -68,18 +72,22 @@ Tags at sourceforge.net CVS
- snapshot releases at
http://sofia-sip.sourceforge.net/snapshots/
Notes (*):
- Information about Darcs:
http://abridgegame.org/darcs/
http://lwn.net/Articles/110516/
Sending patches
===============
People without CVS-access
-------------------------
People without Darcs access
---------------------------
Send your patches to sofia-sip-devel. Someone from the
development team (see AUTHORS) will handle the patch.
People with CVS-access
----------------------
People with Darcs access
------------------------
Trivial changes can be committed without review. For non-trivial
changes, you should first send a proposal to sofia-sip-devel and
......@@ -89,6 +97,8 @@ common sense is recommended. ;)
Tips for making patches
-----------------------
- test your patch on a clean CVS-checkout
- remember to run cvs update before making commits
- test your patch on a clean checkout from version control system
- remember to check for updates before pushing your changes
to the master repository
......@@ -3,14 +3,13 @@ Sofia-SIP release management README
===================================
:Author: Kai Vehmanen <kai -dot vehmanen -at- nokia -dot- com>
:Version: 20060411-8
:Version: 20060504-9
:Formatting: reStructuredText, http://docutils.sourceforge.net/rst.html
Introduction
============
This README contains instructions for making
new Sofia-SIP releases.
This README contains instructions for making new Sofia-SIP releases.
Links to other resources
========================
......@@ -20,8 +19,7 @@ sofia-sip/README.developers
The release notes
=================
The release notes should contain the following
sections:
The release notes should contain the following sections:
- about Sofia-SIP
- copied verbatim from sofia-sip/README
......@@ -40,19 +38,22 @@ sections:
should list all persons/companies who have code/scripts/etc
copyrighted to them in the sofia-sip tree)
See the RELEASE.template file for a full list of release note
sections.
Making the release tarball
==========================
- update the version number in sofia-sip/configure.ac
- make sure everything that is supposed to be in the
release is in CVS (use commands "cvs up" and "darcs w")
release is in the master darcs tree
- run 'make distcheck' (requires automake-1.7 or newer)
- tag CVS tree and darcs repo with release tag
- tag repos (darcs and any slave trees) with release tag
'rel-sofia-sip-x_y_z', where x_y_z is the version number (see
README.developers):
cvs tag rel-sofia-sip-x_y_z
darcs tag -m"rel-sofia-sip-x_y_z"
cvs tag rel-sofia-sip-x_y_z
- calculate md5 and sha1 hashes using md5sum and sha1sum utils,
and copy the values to the release-notes (see below)
......@@ -69,7 +70,7 @@ Creating the release notes and updating the website
see guidelines in the html comments)
- update sfnet_www/index.html to mention the latest
release
- commit the change to CVS, and run the
- commit the change to sf.net website CVS, and run the
sfnet_www/put_online.sh script at the sourceforge.net
shell server
......@@ -95,9 +96,9 @@ After release
=============
- replace the RELEASE file with RELEASE.template, and
commit it to CVS/darcs.
commit it to master source repository (see sofia-sip/README.developers)
- change version in configure.ac from "X.Y.Z" to
"X.Y.Zcvs" (as it is in many cases unknown what the
"X.Y.Zwork" (as it is in many cases unknown what the
next version will be)
- make a "tree open for development" commit
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment