RE: [tag] Groups - Test Assertions Guidelines draft 0.9.9.6 (TestAssertionsGuidelines-draft-0-9-9-6.doc) uploaded

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

Stephen:

 

Agree the wiki does not need be updated too often , and can lag behind the latest release.

 

I see it mostly convenient to centralise comments in a single place.

 

So its OK to make comments in wiki that explicitly refer to the latest release that can be ahead of the wiki - just add "on-rev0.996" to your comment tag... If the comment is at the right section in the wiki that is still useful.

 

Jacques

---

From: stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] On Behalf Of Stephen Green
Sent: Tuesday, November 18, 2008 1:26 AM
To: Dmitry.Kostovarov@sun.com; Durand, Jacques R.; tag@lists.oasis-open.org
Subject: Re: [tag] Groups - Test Assertions Guidelines draft 0.9.9.6 (TestAssertionsGuidelines-draft-0-9-9-6.doc) uploaded

It's OK for me though we might find it too time consuming to 
keep
the wiki up to date with all changes to the document. For the 
time
being though it seems like a workable 
approach.

Regards

Steve

2008/11/18 Dmitry Kostovarov <Dmitry.Kostovarov@sun.com>

This works for me.

Dima

Durand, Jacques R. wrote:

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
Sent: Sunday, November 16, 2008 8:00 AM
To: tag@lists.oasis-open.org
Subject: Re: [tag] Groups - Test Assertions Guidelines draft 0.9.9.6 (TestAssertionsGuidelines-draft-0-9-9-6.doc) uploaded

Do we agree that this is the version on which we would like Dima (technical writer) to start
working?

2008/11/16 <stephen.green@documentengineeringservices.com>

Public Link:
http://www.oasis-open.org/apps/group_public/download.php/30061/TestAssertionsGuidelines-draft-0-9-9-6.doc


 -- Stephen Green

The document revision named Test Assertions Guidelines draft 0.9.9.6
(TestAssertionsGuidelines-draft-0-9-9-6.doc) has been submitted by Stephen
Green to the OASIS Test Assertions Guidelines (TAG) TC document repository.
 This document is revision #28 of TestAssertionsGuidelines-draft-0-2.odt.

Document Description:
The main output of this committee: Test Assertions Guidelines

View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=30061

Download Document:
http://www.oasis-open.org/committees/download.php/30061/TestAssertionsGuidelines-draft-0-9-9-6.doc

Revision:
This document is revision #28 of TestAssertionsGuidelines-draft-0-2.odt.
The document details page referenced above will show the complete revision
history.


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration

--
Stephen D. Green

Document Engineering Services Ltd



http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice

-- 
Stephen D. Green

Document Engineering Services 
Ltd



http://www.biblegateway.com/passage/?search=matthew+22:37 
.. and voice