DSCM Evaluation Plan

Process

 Each DSCM finalist has a Primary Evaluator assigned from the OpenSolaris I-team:

  • Bazaar, v 0.7, Stephen Hahn
  • GIT, v 1.2.2, Frank van der Linden
  • Mercurial, v 0.8, Mike Kupfer

NOTE: GIT v 1.2.4 was initially the finalist. But problems with local repository support in both v 1.2.4 and 1.2.3 caused us to revert to v 1.2.2.

 The Primary Evaluator is not performing a full quantitative evaluation. Rather, the Primary Evaluator is:

  • understanding how the tools work in detail,
  • testing typical operations and operations known to often cause problems,
  • evaluating the source code to determine whether it is well-constructed and suited for ongoing use and improvement in the OpenSolaris environment.

 The Primary Evaluator will submit a report to the tools-discuss mail list detailing the evaluation results. Additional reports from community members are welcome and encouraged. Reports (see the Evaluation Form) should be sent to the tools-discuss mail list by the deadline (see Schedule below). The Primary Evaluator will roll up this input as part of his report.

Schedule

 Weeks 1 & 2

  • Evaluation and draft report by Primary Evaluator.
  • Draft report sent out at the end of Week 2.

 Week 3

  • Primary Evaluator gets feedback on draft report and works through input/questions sent in during the first two weeks.
  • Community input due by the end of Week 3.

 Week 4

  • Final report generated that includes findings, assessment, community input and information about implementation costs.

 Tentative Dates

  • Week 1 START = 3/20/06 END = 3/24/06
  • Week 2 START = 3/27/06 END = 3/31/06
  • Week 3 START = 4/03/06 END = 4/07/06
  • Week 4 START = 4/10/06 END = 4/14/06
last modified by admin on 2009/10/26 12:11
Collectives
Project


© Sun Microsystems Inc. 2009
XWiki Enterprise 1.8.2.19075 - Documentation
Terms Of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines | Site map | Help
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.