Download Ekiga sources

From Ekiga
(Difference between revisions)
Jump to: navigation, search
(Syncing Branches)
(Syncing Branches)
Line 26: Line 26:
 
* 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 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 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.
+
* 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.
 
* When a feature is added and that this feature is experimental, only the Trunk should be modified. The NEWS file should be updated accordingly.

Revision as of 16:35, 31 December 2006

Active Branches

Ekiga currently has 3 active branches:

  • Trunk: This branch contains the latest development code and experimentation.

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

  • H_Release: This branch contains the latest development code that has been tested and certified to work correctly. It is temporary and is used as a stable base for SIP Presence development.

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

Anonymous Access: svn co http://svn.gnome.org/svn/ekiga/branches/H_Release ekiga

  • gnome-2-14: This branch contains the latest stable code corresponding to the 2.0.x releases.

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

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

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