Download Ekiga sources

From Ekiga
Revision as of 09:48, 15 August 2007 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-20: 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-20 ekiga

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

OPAL / PWLIB Active Branches

OPAL and PWLIB have 2 active branches:

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

See http://sourceforge.net/cvs/?group_id=80674

cvs -z9 -d:pserver:anonymous@openh323.cvs.sourceforge.net:/cvsroot/openh323 co ptlib_unix

cvs -z9 -d:pserver:anonymous@openh323.cvs.sourceforge.net:/cvsroot/openh323 co ptlib_win32

cvs -z9 -d:pserver:anonymous@openh323.cvs.sourceforge.net:/cvsroot/openh323 co opal
  • Phobos: This branch contains the latest stable code corresponding to the Ekiga 2.0.x releases.

See http://sourceforge.net/cvs/?group_id=80674

cvs -z9 -d:pserver:anonymous@openh323.cvs.sourceforge.net:/cvsroot/openh323 co -r Phobos ptlib_unix

cvs -z9 -d:pserver:anonymous@openh323.cvs.sourceforge.net:/cvsroot/openh323 co -r Phobos ptlib_win32

cvs -z9 -d:pserver:anonymous@openh323.cvs.sourceforge.net:/cvsroot/openh323 co -r 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