Changes

Jump to: navigation, search

BTP300 Project Requirements 20113

8 bytes added, 21:03, 4 October 2011
Directory Structure
# Update your team's wiki page with your team's repository path information under '''Repo Path'''
# Create a directory with your seneca id under the branch sub-directory of your team's repository. This will be your home directory for development:
==== Directory Structure ====
<big><pre>
|-- Team_Repository_Account
</pre></big>
===== branches =====
* '''branches''' is the common directory for all team members' workspaces.
* Each team member should create their own home directory or '''workspace''' (member-id1, member-id2,...) for their own development tasks within '''branches'''.
*: ''These sub-directories(Task1, Task2,...) are called branches of trunk. When the word '''branch''' is used as a verb, it means copying the whole '''trunk''' into a sub-directory, either in '''branches''' or '''tags'''.
===== tags =====
* '''tags''' is the directory that holds '''copies''' of successful stages of '''trunk''' throughout development. (''Also called as '''Milestones''''')
* '''tags''' are never modified or edited. ''You may branch a directory of tag into branches under a workspace and then modify the branch and apply the changes back to trunk, but you should never change the contents of a tag''
**: ''If R0.3 is due, and R0.3, R0.31, R0.32 are present in '''tags''', then your instructor will mark R0.32
===== trunk =====
* '''trunk''' is the directory that holds the project in its current stage, '''complied and run-able'''
* '''trunk''' should never hold non-compiled code. Usually trunk is an exact copy (or better than) the latest version in '''tags'''.

Navigation menu