community.egroupware.org: Community wiki

  
Community wiki
CVS

 This is outdated since eGroupWare is using SVN now

Have a look here: http://www.egroupware.org/wiki/subversion

  


  

Usefull other resources about CVS and administrative tasks in CVS:

  • to checkout / update eGroupWare via CVS
  • Cederqvist [CVS manual] everything u need to know

importing new sources into our CVS repository

Process of importing the 2 code-lines of the new wiki app into our cvs:
  1. cd /path/to/egroupware
  2. Importing the original Tavi Sources http://tavi.sf.net of their release 0.22 into the vendor branch/tag 'TAVI' and release tag 'TAVI-0_22':
    • cvs -d:ext:ralfbecker@sourceforge.net:/cvsroot/egroupware -z3 import -m "Import of Tavi's 0.22 release" wiki TAVI TAVI-0_22
  3. Importing the Axis port http://www.axisgroupware.org of there release 0.44 into the vendor branch/tag 'AXIS' and the release tag 'AXIS-0_44':
    • cvs -d:ext:ralfbecker@sourceforge.net:/cvsroot/egroupware -z3 import -b 1.1.3 -m "Import of Axis's 0.44 release" wiki AXIS AXIS-0_44
  4. checkout of Axis release to resolve conflicts:
    • cvs -d:ext:ralfbecker@sourceforge.net:/cvsroot/egroupware checkout -jTAVI -jAXIS wiki
  5. make it the head-version by commiting the changes of the merge:
    • cd wiki
    • cvs commit -m "summary of change"
If u only need to import one code-line, u can skip the steps 3 to 5 and just do a:
  • cvs co wiki

taging a new release, bugfix-release or release-candicate

cvs rtag -r <branch-tag> <new-tag> all

<branch-tag> is the tag of the (stable) branch, eg. 'Version-0_9_14-branch', which should get tagged. <new-tag> is the name of the tag to create, eg. 'Version-0_9_14-0_0_2' or 'Version-0_9_14-final'.
Other administrative tasks to create a new (stable) branch, no related to CVS:
  • for the final release you have to increment the version-number in phpgwapi/inc/setup.inc.php and create an update_tables.inc.php to install the new number in the db, before u tag the relase
  • ...

moveing a release-tag

cvs rtag -r <branch-tag> -F <tag> all

<branch-tag> is the tag of the (stable) branch, eg. 'Version-0_9_14-branch', where <tag> is the name of the tag to be moved, eg. 'Version-0_9_14-branch-0_0_5'.

creating a new release branch

cvs rtag -r <base-branch-tag> -b <new-branch-tag> all

The -r <base-branch-tag> is only necessary if the branch is not based on (HEAD)? (like eg. the 0.9.16 branch which is based on 0.9.14). You can use a list of modules instead of all, if some modules / apps should not be included in the branch.
Other administrative tasks to create a new (stable) branch, no related to CVS:
  • if branch is not based on HEAD you should decrement the version-number in phpgwapi/inc/setup.inc.php and create an update_tables.inc.php to install the new number in the db
  • ...

compiled by ralfbecker



You are here