Changes between Version 2 and Version 3 of WikiStart


Ignore:
Timestamp:
2005-07-01T10:41:20Z (20 years ago)
Author:
frcm
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v2 v3  
    44The system allows for browsing through the history of source code, documentation and test folders
    55for various versions. Tickets for feature requests, bugs or any other issues with ROPP can be
    6 created and tracked. The system is based on Trac and intended to be used together with [http://www-nwp/~frtc/FCM/trunk/doc/sys/user_guide/index.html FCM].
     6created and tracked. The system, which supports Subversion and FCM, is based on Trac.
    77
     8
     9== About Subversion ==
     10
     11[http://subversion.tigris.org/ Subversion] is a version control system meant to be a replacement for CVS,
     12and has most of CVS's features. Generally, Subversion's interface to a particular feature is similar to CVS's,
     13except where there's a compelling reason to do otherwise. The most important advantage over CVS is that
     14Subversion does not only version file contents and file existence, but also directories, copies, and renames.
     15Commits are also truly atomic; no part of a commit takes effect until the entire commit has succeeded. The most
     16visible difference to CVS is that CVS Revision numbers are per-commit, not per-file. Tags and branches are also handled somewhat differently (rather like copying things into dedicated directories).
     17
     18Probably the best source about Subversion is the [http://svnbook.red-bean.com/nightly/en/index.html Subversion book]
     19(the link points to the current development version of the documentation; pdf and other versions of the book are
     20[http://svnbook.red-bean.com/ available here].
     21
     22Users without experience in version control systems like Subversion or CVS might benefit from this [http://svnbook.red-bean.com/nightly/en/svn.intro.html general introduction]; experienced CVS users will find
     23[http://svnbook.red-bean.com/nightly/en/svn.forcvs.html Subversion for CVS users] useful.
     24
     25The subversion repository for ROPP can be accessed via the Subversion server at the URL
     26{{{
     27svn://eld001/ROPP_svn/...
     28}}}
     29For example, checking out the actual development version of the entire source code into a subdirectory ropp_src would require
     30{{{
     31svn co svn://eld001/ROPP_svn/ropp_src/trunk ropp_src
     32}}}
     33The commands
     34{{{
     35svn co svn://eld001/ROPP_svn/ropp_doc/trunk ropp_doc
     36svn co svn://eld001/ROPP_svn/ropp_web/trunk ropp_web
     37svn co svn://eld001/ROPP_svn/ropp_test/trunk ropp_test
     38}}}
     39will check out the documentation, web presentation, and test folder in a similar way. With FCM (see below), the
     40above checkout commands would be somewhat simpler:
     41{{{
     42fcm co fcm:ropp_src_tr ropp_src
     43fcm co fcm:ropp_doc_tr ropp_doc
     44fcm co fcm:ropp_web_tr ropp_web
     45fcm co fcm:ropp_test_tr ropp_test
     46}}}
     47The latter requires that FCM is set up properly in your environment.
     48
     49
     50== About FCM ==
    851 
     52[http://www-nwp/~frtc/FCM/trunk/doc/sys/user_guide/index.html FCM] (Flexible Configuration Management
     53system) is the Met Office's set of tools build around Subversion (for version management), Trac
     54(for issue tracking) and the Met Office's own build system. ROPP uses FCM only for code management; the
     55build part is based on GNU's autotools. The
     56[http://www-nwp/~frtc/FCM/trunk/doc/sys/user_guide/index.html documentation for FCM] is quite exhaustive;
     57to access the FCM commands the following command needs to be added to your .profile (or equivalent shell
     58initialisation file):
     59
     60{{{
     61. ~frdm/FCM/bin/env.sh
     62}}}
     63
     64Among the advantages of using FCM is a simpler frontend to Subversion commands (see the checkout examples above),
     65but also and graphical diff and merge utilities. In order to support ROPP, the following abbreviations/keywords
     66are implemented within FCM:
     67
     68{{{
     69fcm:ropp_doc         svn://eld001/ROPP_svn/ropp_doc
     70fcm:ropp_doc_tr      svn://eld001/ROPP_svn/ropp_doc/trunk
     71fcm:ropp_doc_br      svn://eld001/ROPP_svn/ropp_doc/branches
     72fcm:ropp_doc_tg      svn://eld001/ROPP_svn/ropp_doc/tags
     73fcm:ropp_src         svn://eld001/ROPP_svn/ropp_src
     74fcm:ropp_src_tr      svn://eld001/ROPP_svn/ropp_src/trunk
     75fcm:ropp_src_br      svn://eld001/ROPP_svn/ropp_src/branches
     76fcm:ropp_src_tg      svn://eld001/ROPP_svn/ropp_src/tags
     77fcm:ropp_test        svn://eld001/ROPP_svn/ropp_test
     78fcm:ropp_test_tr     svn://eld001/ROPP_svn/ropp_test/trunk
     79fcm:ropp_test_br     svn://eld001/ROPP_svn/ropp_test/branches
     80fcm:ropp_test_tg     svn://eld001/ROPP_svn/ropp_test/tags
     81fcm:ropp_web         svn://eld001/ROPP_svn/ropp_web
     82fcm:ropp_web_tr      svn://eld001/ROPP_svn/ropp_web/trunk
     83fcm:ropp_web_br      svn://eld001/ROPP_svn/ropp_web/branches
     84fcm:ropp_web_tg      svn://eld001/ROPP_svn/ropp_web/tags
     85}}}
     86
     87
    988== About Trac ==
    1089
    11 Trac is a '''minimalistic''' approach to '''web-based''' management of
    12 '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress.
     90[http://trac.edgewall.com/ Trac] is a minimalistic approach to web-based management of
     91software projects. Its goal is to simplify effective tracking and handling of software issues,
     92enhancements and overall progress. All aspects of Trac have been designed with the single goal
     93to help developers write software while staying out of the way and imposing as little as possible
     94on a team's established process and culture.
    1395
    14 All aspects of Trac have been designed with the single goal to
    15 '''help developers write great software''' while '''staying out of the way'''
    16 and imposing as little as possible on a team's established process and
    17 culture.
     96There is some [wiki:TracGuide built-in documentation], a [http://projects.edgewall.com/trac/wiki/TracFaq FAQ],
     97and a complete list of [wiki:TitleIndex local wiki pages].
     98
     99
     100
     101== About this page ==
    18102
    19103As all Wiki pages, this page is editable, this means that you can
    … …  
    21105web-browser. Simply click on the "Edit this page" link at the bottom
    22106of the page. WikiFormatting will give you a detailed description of
    23 available Wiki formatting commands.
     107available Wiki formatting commands. The [wiki:TracGuide Trac documentation]
     108will also help you get started.
    24109
    25 "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created
    26 a new Trac environment, containing a default set of wiki pages and some sample
    27 data. This newly created environment also contains
    28 [wiki:TracGuide documentation] to help you get started with your project.
    29 
    30 You can use [wiki:TracAdmin trac-admin] to configure
    31 [http://trac.edgewall.com/ Trac] to better fit your project, especially in
    32 regard to ''components'', ''versions'' and ''milestones''.
     110It is possible to configure Trac to better fit this project, especially in regard to ''components'',
     111''versions'' and ''milestones''. At present, however, this is only possible on a system administrator level;
     112so contact Dave Matthews about such changes.
    33113
    34114
    35 == Starting Points for TRAC ==
    36 
    37  * TracGuide --  Built-in Documentation
    38  * [http://projects.edgewall.com/trac/ The Trac project] -- Trac Open Source Project
    39  * [http://projects.edgewall.com/trac/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions
    40  * TracSupport --  Trac Support
    41 
    42 For a complete list of local wiki pages, see TitleIndex.
    43