SVN
From Ekiga
[edit]
Ekiga/OPAL/PTLIB Active Branches
The triplet Ekiga/OPAL/PTLIB currently has 2 active branches:
- Trunk: This branch contains the latest development code. It will make up a future release 3.2.0.
svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/trunk ptlib
svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/trunk opal
svn co http://svn.gnome.org/svn/ekiga/trunk ekiga
Developer access to Ekiga: svn co svn+ssh://[login@]svn.gnome.org/svn/ekiga/trunk ekiga
- gnome-2-24: This branch contains the latest stable code corresponding to the Ekiga 3.0.x releases.
svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/branches/v2_4 ptlib
svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/branches/v3_4 opal
svn co http://svn.gnome.org/svn/ekiga/branches/gnome-2-24 ekiga
Developer access to Ekiga: svn co svn+ssh://[login@]svn.gnome.org/svn/ekiga/branches/gnome-2-24 ekiga
[edit]
Useful Links
- Web Interface:
- SVN Tutorial: http://developer.gnome.org/tools/svn.html
[edit]
Syncing Branches
- When a bugfix that affects all branches is committed, all branches should be updated as well as the NEWS file.
- When a bugfix that affects one specific branch is committed, only that branch should be updated as well as the NEWS file. If that bugfix is specific to the Trunk and fixes a bug introduced in the Trunk during the development phase, the NEWS file should not be updated.
- When a feature is added and that this feature is considered as stable, it should be added to the Trunk and to the H_Release branch. Both NEWS files should be modified accordingly. New features should not be committed to the gnome-2-14 branch. Non-critical fixes that break strings should not be committed to the gnome-2-14 branch.
- When a feature is added and that this feature is experimental, only the Trunk should be modified. The NEWS file should be updated accordingly.
