The Jerome SVN has the following structure.

jerome
-jerome
     -trunk (contains the currently worked on version)
     -tags (any released versions of jerome)
     -branches (contains both, imported sword versions, and branches of jerome)
-icu-sword
     -trunk (contains the latest import of icu-sword)
-jeromew
    -trunk (contains the currenlty worked on version of jerome version of biblecs)
    -tags (any released versions of jeromew)
    -branches (contains both, imported biblecs versions, and branches of jeromew)


This will allow the following tasks with an explanation of the steps involved in each.

1) update jerome to a more recent version of sword
   a) create a jerome/jerome/branch/sword[version number] folder
   b) import sword into it.
   c) create a jerome/jerome/branch/jerome[same version number as sword] folder
   d) merge jerome/jerome/trunk/ with jerome/jerome/branch/sword[version number] into jerome/jerome/branch/jerome[same version number as sword] folder
   e) test it, and test it again.
   f) tag jerome/jerome/trunk into a new tag jerome/jerome/tag/jerome[the previous version of sword].[jerome development increment]
   g) copy jerome/jerome/branch/jerome[same version number as sword] into jerome/jerome/trunk
   h) make an announcement on mailing list.

2) update jeromew to a more recent version of biblecs.
   follow the same proceedure as 1)

3) modify jerome
   a) create a branch of jerome with a title that describes the aim of the modification.
   b) go for it.
   c) if it works and is accepted, then integrate into trunk.

4) modify jeromew
   same as 3)

Note: It is expected that we will only be modifying specific files so most updating should be a simple merge.

Any added features should be worked on with sword directly through their development processes. We only want to ensure deuteros are integrated.