53 | | The instructions above will enable any registered user to get a copy of the codebase. However, any new code by authorized developers must be committed to the repository on a branch. There are many |
| 55 | The instructions above will enable any registered user to get a copy of the ''`trunk`'' or current codebase. Any new code by authorized developers, however, must be committed to the repository on a ''`branch`''. The details of merging and branching are outlined in detail in [http://svnbook.red-bean.com/ The SVN Book] and we encourage everyone involved to keep it handy. Some very basic instructions and guidelines are provided below. |
| 56 | [[BR]][[BR]] |
| 57 | |
| 58 | == Branching == |
| 59 | OpenSHA development occurs on branches. To create a branch: |
| 60 | |
| 61 | * Switch to the ''`SVN Repository Exploring`'' perspective (see step 3 above). |
| 62 | * Right click on ''`trunk`'' and select ''`Branch/Tag...`'': |
| 63 | [[Image(http://intensity.usc.edu/trac/opensha/attachment/wiki/SettingUpEclipse/svn_branch.png?format=raw)]] |
| 64 | |
| 65 | * In the window that follows, enter: |
| 66 | `http://intensity.usc.edu/svn/opensha/branches/username_branchname` |
| 67 | (replace ''`username`'' and ''`branchname`'' as appropriate) |
| 68 | |
| 69 | * Click ''`Finish`'' (or ''`Next`'' for more advanced options). |
| 70 | |
| 71 | |
| 72 | == Merging == |
| 73 | |
| 74 | |
| 75 | |