| 6 | | All aspects of Trac have been designed with the single goal to |
| 7 | | '''help developers write great software''' while '''staying out of the way''' |
| 8 | | and imposing as little as possible on a team's established process and |
| 9 | | culture. |
| | 5 | == Some basics == |
| | 6 | * Trac - This wiki specialised to provide tools useful for managing or tracking a project. The buttons along the top lead to useful functions. |
| | 7 | * '''Browse source''' shows the file system we have set up in subversion. |
| | 8 | * '''Timeline''' shows what changes have been made recently, and by whom. |
| | 9 | * '''New ticket''' allows bugs or new tasks to be entered as a ticket, and '''View tickets''' gives various views of those tickets. |
| | 10 | * subversion (svn) is the version control system used. |
| | 11 | * A good reference is [http://svnbook.red-bean.com/] |
| | 12 | * [http://svnbook.red-bean.com/en/1.0/ch09.html Quick guide to svn commands] (chapter 9 of red-bean). |
| 11 | | As all Wiki pages, this page is editable, this means that you can |
| 12 | | modify the contents of this page simply by using your |
| 13 | | web-browser. Simply click on the "Edit this page" link at the bottom |
| 14 | | of the page. WikiFormatting will give you a detailed description of |
| 15 | | available Wiki formatting commands. |
| 16 | | |
| 17 | | "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created |
| 18 | | a new Trac environment, containing a default set of wiki pages and some sample |
| 19 | | data. This newly created environment also contains |
| 20 | | [wiki:TracGuide documentation] to help you get started with your project. |
| 21 | | |
| 22 | | You can use [wiki:TracAdmin trac-admin] to configure |
| 23 | | [http://trac.edgewall.org/ Trac] to better fit your project, especially in |
| 24 | | regard to ''components'', ''versions'' and ''milestones''. |
| 25 | | |
| 26 | | |
| 27 | | TracGuide is a good place to start. |
| 28 | | |
| 29 | | Enjoy! [[BR]] |
| 30 | | ''The Trac Team'' |
| | 14 | == Using the repository == |
| | 15 | 1. We have set up the svn repository with the following structure: |
| | 16 | {{{ |
| | 17 | trunk/ |
| | 18 | Darwin/ |
| | 19 | bin/ |
| | 20 | Makefile |
| | 21 | Linux/ |
| | 22 | bin/ |
| | 23 | Makefile |
| | 24 | scripts/ |
| | 25 | src/ |
| | 26 | SunOS/ |
| | 27 | bin/ |
| | 28 | Makefile |
| | 29 | Makefile |
| | 30 | }}} |
| | 31 | * All the FORTRAN source is in src/. |
| | 32 | * The main Makefile is in the top (trunk) directory. |
| | 33 | * The architecture directories (Darwin, Linux, SunOS) contain supplementary Makefiles that set architecture-specific symbols, and bin/ directories to receive the binaries. |
| | 34 | 1. The URL for the repository is https://svn.atnf.csiro.au/parkespol In a browser that address will bring you to this page. In svn that address will give access to the repository. |
| | 35 | 1. A typical cycle for changing the code is: |
| | 36 | * Make your own personal working version of the whole tree |
| | 37 | {{{ |
| | 38 | svn checkout https://svn.atf.csiro.au/parkespol myWorking/ |
| | 39 | }}} |
| | 40 | * make changes, and test compilation and execution |
| | 41 | * Commit changes to the repository. Describe changes in the log required by the svn commit command. |
| | 42 | {{{ |
| | 43 | svn commit https://svn.atnf.csiro.au/parkespol |
| | 44 | }}} |
