[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tag] Groups - Test Assertions Guidelines draft 0.9.9.6 (TestAssertionsGuidelines-draft-0-9-9-6.doc) uploaded
Yes, -Cho From: Durand, Jacques R.
[mailto:JDurand@us.fujitsu.com] Yes - now of course that does not
mean the doc has to freeze until Dima gives the first round of feedback /
suggestions. Stephen: one way to manage this
kind of "concurrent editing" , is via the wiki (as tagged comments as
usual) We can then synchronize
frequently, say every 2-week, if editors are OK working on a moving target. So the process could be like: - the formal spec rev (0.996) is
for now the official one that editors (Dima and Stephen) work from. - any ongoing suggestions or
requests for edits from the TC, would go in the wiki - both editors look at
these comments, possibly discuss them on wiki. If of editorial
nature, editors can make the decision to factor these in their currently
revised draft, say 0.997. If of technical nature, they get on the TC agenda for
discussion. - editor(s) circulate a proposed
revision for next meeting (2-week period) or earlier if they feel like it. As
soon as the new Editors' draft is out, it serve as basis for next round of
edits/review. Would that work for everyone? Jacques From:
stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] On Behalf Of Stephen
Green Do we agree that this is the version on which we would
like Dima (technical writer) to start 2008/11/16 <stephen.green@documentengineeringservices.com> Public Link:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]