| This manual is deprecated. Please visit https://groupoffice.readthedocs.io for the latest documentation. |
Difference between revisions of "Subversion"
(New page: To start developing you'll need the source. Intermesh uses the subversion service from Sourceforge. There are a couple of top level directories that are important: 1. branches 2. tags 3. ...) |
|||
| Line 2: | Line 2: | ||
There are a couple of top level directories that are important: | There are a couple of top level directories that are important: | ||
| − | 1. branches | + | *1. branches |
| − | 2. tags | + | *2. tags |
| − | 3. trunk | + | *3. trunk |
The most important branches are the release branches. For example the code from the 2.16 release is stored in branches/groupoffice-com-2.16. When we release a version then we copy the source from branches/groupoffice-com-2.16 to tags/groupoffice-com-2.16-1 for example. When a bug is discovered in 2.16 then we fix it in the trunk then we merge this bugfix into the groupoffice-com-2.16 branch and after that we copy the branch to a new tag. | The most important branches are the release branches. For example the code from the 2.16 release is stored in branches/groupoffice-com-2.16. When we release a version then we copy the source from branches/groupoffice-com-2.16 to tags/groupoffice-com-2.16-1 for example. When a bug is discovered in 2.16 then we fix it in the trunk then we merge this bugfix into the groupoffice-com-2.16 branch and after that we copy the branch to a new tag. | ||
Revision as of 14:10, 29 September 2008
To start developing you'll need the source. Intermesh uses the subversion service from Sourceforge. There are a couple of top level directories that are important:
- 1. branches
- 2. tags
- 3. trunk
The most important branches are the release branches. For example the code from the 2.16 release is stored in branches/groupoffice-com-2.16. When we release a version then we copy the source from branches/groupoffice-com-2.16 to tags/groupoffice-com-2.16-1 for example. When a bug is discovered in 2.16 then we fix it in the trunk then we merge this bugfix into the groupoffice-com-2.16 branch and after that we copy the branch to a new tag.
This way we can develop new features inside the trunk and only put bugfixes in the stable release branch and we don't get new untested features into the stable release branches.
Click here to browse the Group-Office subversion repository
To checkout the latest trunk for do:
svn checkout https://anonymous@group- \ office.svn.sourceforge.net/svnroot/group-office/branches/ \ groupoffice-com-2.17
