Using svn and trac: rough sketch

MURATA Makoto eb2m-mrt at asahi-net.or.jp
Wed May 13 16:28:32 CEST 2009


Dear colleagues,

I have been thinking about the use of subversion for OOXML schemas.
We have to consider a number of issues: development of DCORs
and (F)PDAMS in parallel, relationship between DRs and schema
changes, automatic generation of schemas.

Here is my rough sketch about the use of svn.  Comments are very
welcome.  Since I know nothing about trac and very little about svn,
I might have made serious mistakes.  Comments are very welcome.


1. General

1) Use the combination of subversion and trac on assembla.com.

2) Export both the svn repository and the trac repository
    periodically.


2. Issue tracking using trac

1) Register every DR as a trac ticket.

2) Register every amendment project as a trac ticket, if the scope
  of the project is more than DRs.

3) Create a program that extract DRs from the DR log (an Word2007
  document) or the DR index (an Excel book) and submit them as trac
  tickets.  Note that the end of the following page shows the URI
  syntax for registering tickets.

    http://trac.edgewall.org/wiki/TracTickets

4) Configure subversion so that a trac ticket number is
  required whenever a schema module is committed.

5) One ticket at a time:  Do not use "commit" for more than one ticket.

Question: In trac, should we register the DR number only?  Or, should
we register everything about the DR?


3. RNG/XSD and strict/transitional

1) Store all four combinations (RNG/XSD * strict/transitional) of
  OOXML schemas in the subversion repository.

2) If the four combinations are created from some authoritative source, store
  that authoriative source in the repository as well.

3) Develop conversion programs from the authoritative source to the four
  combinations and store the programs in the repository as well.


4. AM sets and COR sets

1) Create a svn tag whenever an edition of 29500, a COR set, or an AM
set is published.

2) Create a branch whenever a project for an AM set is started.

3) Whenever an amendment project successfully results in an AM set,
  merge the branch back to trunk.


Cheers,


Makoto <EB2M-MRT at asahi-net.or.jp>



More information about the sc34wg4 mailing list