Changes between Version 18 and Version 19 of ropp_repository
- Timestamp:
- 2020-01-13T15:46:45Z (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ropp_repository
v18 v19 13 13 For a complete list of Subversion commands see the [http://svnbook.red-bean.com/en/1.0/index.html SVN reference manual] 14 14 15 '''Checking out trunk''' 15 === Checking out the trunk === 16 16 17 17 To [http://svnbook.red-bean.com/en/1.0/re04.html checkout] the latest development (trunk) versions: … … 23 23 This will check out the source code (with build support), documentation, and test folder, respectively to the local working directory. 24 24 25 '''Checking out old release versions''' 25 === Checking out old release versions === 26 26 27 27 To checkout the older (tagged) release versions: … … 37 37 A [http://svnbook.red-bean.com/en/1.0/ch04s06.html tag] is just [http://svnbook.red-bean.com/en/1.0/re07.html copy] or snapshot of a a particular revision of the repository. In the case of ROPP, a copy taken from the head of trunk at the time that the distribution files for a release were built. You could just as well checkout the revision number instead, but a tag is easier to remember. 38 38 39 == Branches==39 === Branches === 40 40 41 41 Developments to ROPP should be made from, and committed to, a [http://svnbook.red-bean.com/en/1.0/ch04.html#svn-ch-4-sect-1 branch] rather than directly to the latest trunk version. This allows changes to be tested before merging the required changes back into the trunk. The trunk therefore represents a stable 'next potential release' state for ROPP. Branches can be temporary and might be for working on resolving a specific Trac Ticket.