Commit 892ab2cf authored by Pekka Pessi's avatar Pekka Pessi

README.developers: fixed whitespace

darcs-hash:20081127232817-db55f-db9cd706792bc7c51cca5eb97506e4b0a4b6ad69.gz
parent effb3096
...@@ -6,8 +6,8 @@ Introduction ...@@ -6,8 +6,8 @@ Introduction
============ ============
This file is a collection of practices and rules for Sofia-SIP This file is a collection of practices and rules for Sofia-SIP
development. If you have questions, or would like to make development. If you have questions, or would like to make
changes, raise the issue on sofia-sip-devel (see changes, raise the issue on sofia-sip-devel (see
http://lists.sourceforge.net/lists/listinfo/sofia-sip-devel ). http://lists.sourceforge.net/lists/listinfo/sofia-sip-devel ).
...@@ -15,17 +15,17 @@ Important files for developers ...@@ -15,17 +15,17 @@ Important files for developers
============================== ==============================
AUTHORS AUTHORS
List of contributors. When contributing new code, add List of contributors. When contributing new code, add
yourself to AUTHORS, and also remember to update the yourself to AUTHORS, and also remember to update the
per source file copyright statements. per source file copyright statements.
COPYRIGHTS COPYRIGHTS
List of licenses and related copyright statements. While List of licenses and related copyright statements. While
majority of Sofia-SIP is licensed under LGPL, there are majority of Sofia-SIP is licensed under LGPL, there are
a few files with different, but LGPL compatible, licensing a few files with different, but LGPL compatible, licensing
terms. terms.
README.developers README.developers
This file. This file.
TODO TODO
...@@ -33,11 +33,11 @@ TODO ...@@ -33,11 +33,11 @@ TODO
<dir>/ChangeLog files <dir>/ChangeLog files
All non-trivial changes to the source code should All non-trivial changes to the source code should
be documented in the ChangeLog files. See also the be documented in the ChangeLog files. See also the
top-level ChangeLog. top-level ChangeLog.
Version numbering Version numbering
================= =================
Package version Package version
...@@ -50,8 +50,8 @@ For development releases and snaphots the version is one of: ...@@ -50,8 +50,8 @@ For development releases and snaphots the version is one of:
vMAJOR.MINOR.REVISION, where minor is odd vMAJOR.MINOR.REVISION, where minor is odd
vMAJOR.MINOR.REVISION.YEAR.MONTH.DAY, where minor is odd vMAJOR.MINOR.REVISION.YEAR.MONTH.DAY, where minor is odd
For all releases, the version should be changed in configure.ac For all releases, the version should be changed in configure.ac
and committed to Darcs/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. doing the release is responsible for updating the version number.
Library interface versions Library interface versions
...@@ -64,14 +64,14 @@ Sofia-SIP libraries utilize libtool interface versioning. See ...@@ -64,14 +64,14 @@ Sofia-SIP libraries utilize libtool interface versioning. See
The interface versions are set in top-level 'configure.ac' file. The interface versions are set in top-level 'configure.ac' file.
Additionally, the SONAME version (CURRENT-AGE) is set in the Additionally, the SONAME version (CURRENT-AGE) is set in the
same place. These version numbers are available for use as autoconf same place. These version numbers are available for use as autoconf
variables (see the library 'Makefile.am' files and variables (see the library 'Makefile.am' files and
'packages/sofia-sip.spec.in'). 'packages/sofia-sip.spec.in').
All changes to the library versions should be marked to the All changes to the library versions should be marked to the
appropriate library 'ChangeLog' file. The library version should appropriate library 'ChangeLog' file. The library version should
be changed at the same time as the first interface change is be changed at the same time as the first interface change is
committed since the previous release. The interface version is committed since the previous release. The interface version is
frozen (should be marked to the 'ChangeLog' file) at the time frozen (should be marked to the 'ChangeLog' file) at the time
the next release is tagged (in other words, intra-release changes the next release is tagged (in other words, intra-release changes
need not be tracked with libtool versions). need not be tracked with libtool versions).
...@@ -95,7 +95,7 @@ Tagging releases and snapshots ...@@ -95,7 +95,7 @@ Tagging releases and snapshots
- CVS tree (only used to track major releases) at: - CVS tree (only used to track major releases) at:
http://sourceforge.net/cvs/?group_id=143636 http://sourceforge.net/cvs/?group_id=143636
- tags: rel-sofia-sip-x_y_z - tags: rel-sofia-sip-x_y_z
- stable and development releases (matches release - stable and development releases (matches release
version sofia-sip-x.y.z) version sofia-sip-x.y.z)
- tags: snapshot_rel_YEARMMDD - tags: snapshot_rel_YEARMMDD
- snapshot releases at - snapshot releases at
...@@ -113,13 +113,13 @@ Sending patches ...@@ -113,13 +113,13 @@ Sending patches
People without Darcs access People without Darcs access
--------------------------- ---------------------------
Send your patches to sofia-sip-devel. Someone from the Send your patches to sofia-sip-devel. Someone from the
development team (see AUTHORS) will handle the patch. development team (see AUTHORS) will handle the patch.
People with Darcs access People with Darcs access
------------------------ ------------------------
Trivial changes can be committed without review. For non-trivial Trivial changes can be committed without review. For non-trivial
changes, you should first send a proposal to sofia-sip-devel and changes, you should first send a proposal to sofia-sip-devel and
wait for comments. There are no strict approval rules so use of wait for comments. There are no strict approval rules so use of
common sense is recommended. ;) common sense is recommended. ;)
......
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