= ROPP =

This is the feature request, issue and bug tracking web site for the '''Radio Occultation Processing Package (ROPP)'''.
The system allows for browsing through the history of source code, documentation and test folders 
for various versions. Tickets for feature requests, bugs or any other issues with ROPP can be 
created and tracked. The system, which supports Subversion and FCM, is based on Trac.


== About Subversion ==

[http://subversion.tigris.org/ Subversion] is a version control system meant to be a replacement for CVS, 
and has most of CVS's features. Generally, Subversion's interface to a particular feature is similar to CVS's,
except where there's a compelling reason to do otherwise. The most important advantage over CVS is that 
Subversion does not only version file contents and file existence, but also directories, copies, and renames. 
Commits are also truly atomic; no part of a commit takes effect until the entire commit has succeeded. The most
visible 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).

Probably the best source about Subversion is the [http://svnbook.red-bean.com/nightly/en/index.html Subversion book]
(the link points to the current development version of the documentation; pdf and other versions of the book are 
[http://svnbook.red-bean.com/ available here].

Users 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
[http://svnbook.red-bean.com/nightly/en/svn.forcvs.html Subversion for CVS users] useful.

The subversion repository for ROPP can be accessed via the Subversion server at the URL
{{{
svn://eld001/ROPP_svn/...
}}}
For example, checking out the actual development version of the entire source code into a subdirectory ropp_src would require
{{{
svn co svn://eld001/ROPP_svn/ropp_src/trunk ropp_src
}}}
The commands 
{{{
svn co svn://eld001/ROPP_svn/ropp_doc/trunk ropp_doc
svn co svn://eld001/ROPP_svn/ropp_web/trunk ropp_web
svn co svn://eld001/ROPP_svn/ropp_test/trunk ropp_test
}}}
will check out the documentation, web presentation, and test folder in a similar way. With FCM (see below), the 
above checkout commands would be somewhat simpler:
{{{
fcm co fcm:ropp_src_tr ropp_src
fcm co fcm:ropp_doc_tr ropp_doc
fcm co fcm:ropp_web_tr ropp_web
fcm co fcm:ropp_test_tr ropp_test
}}}
The latter requires that FCM is set up properly in your environment.


== About FCM ==
 
[http://www-nwp/~frtc/FCM/trunk/doc/sys/user_guide/index.html FCM] (Flexible Configuration Management
system) is the Met Office's set of tools build around Subversion (for version management), Trac 
(for issue tracking) and the Met Office's own build system. ROPP uses FCM only for code management; the
build part is based on GNU's autotools. The 
[http://www-nwp/~frtc/FCM/trunk/doc/sys/user_guide/index.html documentation for FCM] is quite exhaustive;
to access the FCM commands the following command needs to be added to your .profile (or equivalent shell 
initialisation file):

{{{
. ~frdm/FCM/bin/env.sh
}}}

Among the advantages of using FCM is a simpler frontend to Subversion commands (see the checkout examples above), 
but also and graphical diff and merge utilities. In order to support ROPP, the following abbreviations/keywords 
are implemented within FCM:

{{{
fcm:ropp_doc         svn://eld001/ROPP_svn/ropp_doc
fcm:ropp_doc_tr      svn://eld001/ROPP_svn/ropp_doc/trunk
fcm:ropp_doc_br      svn://eld001/ROPP_svn/ropp_doc/branches
fcm:ropp_doc_tg      svn://eld001/ROPP_svn/ropp_doc/tags
fcm:ropp_src         svn://eld001/ROPP_svn/ropp_src
fcm:ropp_src_tr      svn://eld001/ROPP_svn/ropp_src/trunk
fcm:ropp_src_br      svn://eld001/ROPP_svn/ropp_src/branches
fcm:ropp_src_tg      svn://eld001/ROPP_svn/ropp_src/tags
fcm:ropp_test        svn://eld001/ROPP_svn/ropp_test
fcm:ropp_test_tr     svn://eld001/ROPP_svn/ropp_test/trunk
fcm:ropp_test_br     svn://eld001/ROPP_svn/ropp_test/branches
fcm:ropp_test_tg     svn://eld001/ROPP_svn/ropp_test/tags
fcm:ropp_web         svn://eld001/ROPP_svn/ropp_web
fcm:ropp_web_tr      svn://eld001/ROPP_svn/ropp_web/trunk
fcm:ropp_web_br      svn://eld001/ROPP_svn/ropp_web/branches
fcm:ropp_web_tg      svn://eld001/ROPP_svn/ropp_web/tags
}}}


== About Trac ==

[http://trac.edgewall.com/ Trac] is a minimalistic approach to web-based management of
software projects. Its goal is to simplify effective tracking and handling of software issues,
enhancements and overall progress. All aspects of Trac have been designed with the single goal 
to help developers write software while staying out of the way and imposing as little as possible 
on a team's established process and culture.

There is some [wiki:TracGuide built-in documentation], a [http://projects.edgewall.com/trac/wiki/TracFaq FAQ], 
and a complete list of [wiki:TitleIndex local wiki pages].



== About this page ==

As all Wiki pages, this page is editable, this means that you can
modify the contents of this page simply by using your
web-browser. Simply click on the "Edit this page" link at the bottom
of the page. WikiFormatting will give you a detailed description of
available Wiki formatting commands. The [wiki:TracGuide Trac documentation]
will also help you get started.

It is possible to configure Trac to better fit this project, especially in regard to ''components'', 
''versions'' and ''milestones''. At present, however, this is only possible on a system administrator level;
so contact Dave Matthews about such changes.