Changes

|-- Team Repository AccountTeam_Repository_Account

| +-- member id one -id1 <-- this is the student's home in branches or "development directory" | +-- Task 1Task1 | +-- Task 2Task2 | +-- member id two-id2 | +-- Task 1Task1 | +-- Task 2Task2 | +-- Task 3Task3 | +-- member id three-id3 | +-- Task 1Task1

* '''Branches''' is a common place for all team members workspace roots' workspaces. * Each team member should have create a home directory or '''workspace''' (workspacemember-id1, member-id2,...) for his own development tasks (workspaces)in branches. Each * The team -member's directory should be workspace is then divided into in several directories for each task in (workspaces) during the development of the project. These workspaces(Task1, Task2, ...) are usually copies of the '''trunk ''' to be worked on.*: ''These directories(projectTask1, Task2,...) developmentare called branches of trunk. Usually each task Also Note that when the word '''branch''' is used as a verb, it means copying the whole trunk into a copy (subdirectory, either in '''Branches''' or '''tags'''.=== Tags ===* '''tags''' directory holds '''copies''' of successful stages of '''trunk''' during development. * '''tags''' are never modified or edited. ''You may branch) the a directory of tag into branches under a workspace and then modify it and apply the changes back to trunk, but the contents of a tag should never change''* The action of '''branching''' the trunk into '''tags''' is often referred to as a '''release'''.* Most importantly, we use the '''tags''' directory to submit the work to the professor to be marked. ''Your professor will specify what are the requirements of a release.** A release is usual tagged by a version like: R0.1, Prj0.2, As1_1.0 ** When a release is due, always the latest version of that realease will be marked. **: ''If R0.3 is due, and in '''tags''' R0.3, R0.31, R0.32 are present, then R0.32 will be marked