Download Ekiga sources

From Ekiga
Revision as of 15:45, 10 March 2008 by Dsandras (Talk | contribs)
Jump to: navigation, search

Contents

Ekiga Active Branches

Ekiga currently has 2 active branches:

  • Trunk: This branch contains the latest development code and experimentation. It works with PWLIB and OPAL HEAD.

Developers Access: svn co svn+ssh://[login@]svn.gnome.org/svn/ekiga/trunk ekiga

Anonymous Access: svn co http://svn.gnome.org/svn/ekiga/trunk ekiga

  • gnome-2-22: This branch contains the latest stable code corresponding to the 2.0.x releases. It works with PWLIB and OPAL Phobos.

Developers Access: svn co svn+ssh://[login@]svn.gnome.org/svn/ekiga/branches/gnome-2-22 ekiga

Anonymous Access: svn co http://svn.gnome.org/svn/ekiga/branches/gnome-2-22 ekiga

OPAL / PTLIB Active Branches

Emblem-important.png PWLib has been renamed under PTLib, and code has been moved from CVS to SVN (Further informations here: http://www.opalvoip.org ) 10-19-2007

OPAL and PTLIB (aka PWLIB) have 2 active branches:

  • Trunk: This branch contains the latest development code and experimentation. It works with Ekiga Trunk.

See http://www.opalvoip.org

svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/trunk ptlib

svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/trunk opal
  • Phobos: This branch contains the latest stable code corresponding to the Ekiga 2.0.x releases.

See http://www.opalvoip.org

svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/branches/Phobos ptlib

svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/branches/Phobos opal

Useful Links

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.
Personal tools