Changes between Version 9 and Version 10 of DevelopersCorner
- Timestamp:
- Mar 6, 2008, 5:03:46 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevelopersCorner
v9 v10 11 11 This is the main development area for Fusion and is always the most up-to-date version. It will typically be somewhat unstable and should not be used for deploying applications. 12 12 '''branches''': 13 Releases of Fusion are organized into branches. When a new major or minor release is made, it is copied from trunk to the branches folder and named {{{fusion-<major> -<minor>}}}. Any bug fixes related to that version are applied to the branch and new bugfix releases can be created from the branch from time to time. A branch is considered stable and usable for deploying applications.13 Releases of Fusion are organized into branches. When a new major or minor release is made, it is copied from trunk to the branches folder and named {{{fusion-<major>.<minor>}}}. Any bug fixes related to that version are applied to the branch and new bugfix releases can be created from the branch from time to time. A branch is considered stable and usable for deploying applications. 14 14 '''tags''': 15 All major, minor and bugfix releases of Fusion are tagged by copying the appropriate branch revision to the tags folder . Binary releases are created by checking out a tag sub folder and running the build process against that folder. You should not commit any changes to a tag.15 All major, minor and bugfix releases of Fusion are tagged by copying the appropriate branch revision to the tags folder and named {{{fusion-<major>.<minor>.<bugfix>}}}. Binary releases are created by checking out a tag sub folder and running the build process against that folder. You should not commit any changes to a tag. 16 16 '''sandbox''': 17 17 Everyone who is a Fusion developer should have a sandbox folder to use for testing out new ideas and implementing specific functionality. Sandbox directories can be used for anything you like. … … 19 19 === Using SVN === 20 20 21 To check out a copy of '''trunk''', a branch, a tagged version, or a sandbox, you need to know the ''URL'' and use {{{svn checkout <url>}}}. For instance: 22 23 * {{{svn co http://svn.osgeo.org/fusion/trunk}}} - check out trunk 24 * {{{svn co http://svn.osgeo.org/fusion/branches/fusion-1.0}}} - check out the branch for version 1.0 25 * {{{svn co http://svn.osgeo.org/fusion/tags/fusion-1.0.0}}} - check out the 1.0.0 released version 26 * {{{svn co http://svn.osgeo.org/fusion/sandbox/pagameba}}} - check out pagameba's sandbox 27 28 Once you have a checked out copy, this is called a working copy. To update a working copy to the latest version, you use the ''update'' command with no arguments: 29 30 * {{{svn update}}} 31 32 To move the working copy to a specific revision number, you can add the ''revision'' parameter: 33 34 * {{{svn update -r <revision>}}} 35 36 To see if you have changes in your working copy against the current revision: 37 38 * {{{svn status}}} 39 40 To see the differences between your working copy and the current revision: 41 42 * {{{svn diff}}} 43 * {{{svn diff > diff.patch}}} redirects the output to a file that is suitable for using with the {{{patch}}} command 44 21 45 == The Build Process == 22 46