[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [chairs] Recommendations for Version Control System!
Hi Sanjay, We haven't used a VCS on the EKMI TC, but will probably do so when we get to the interoperability test-suite goal of the TC. I have personal experience with SCCS, CVS and SVN and vote for SVN if one standard is to be chosen by OASIS. Arshad Noor StrongAuth, Inc. Patil, Sanjay wrote: > > Hi Mary and Chairs of the OASIS TCs, > > I would like to seek your input regarding selection of a Version Control > System (VCS) for use by the OpenCSA TCs. > > Most of the TCs under the OpenCSA Member Section are chartered to > deliver a test suite (for testing conformant implementations). For the > sake of consistency and reuse, the various OpenCSA TCs are planning to > collaborate in developing the different parts of the test suite (test > harness, test cases, etc). As you can imagine, this effort requires > using a Version Control System (VCS) that is more powerful and flexible > than what is currently provided by Kavi. Using SourceForge > infrastructure would be one option in this regard. However before making > any decision, we would like to know if you have any recommendations for > VCS based on the experiences of your TC, any known issues such as user > account management, IPR, etc. > > I am posting the above inquiry on behalf of the OpenCSA Steering > Committee's Liaison Subcommittee which is planning to meet on coming > Thursday (10/23). Your response before coming Thursday is therefore > greatly appreciated. > > Regards, > Sanjay > Co-Chair - OpenCSA Liaison Subcommittee >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]