RE: [tag] TestAssertionsGuidelines-draft-0-9-9-9-in-progress-1.doc

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

So the process now would be:

- tomorrow (Wed) we approve this V0.999 as a Committee Draft (CD).
- This Wed, decide of last proposed pending updates if needed, then
Dimitri review. 
Both result in a new draft produced by Tuesday 27.
- Wed 28 we start an electronic ballot (1 week) for  approving the
latest, as both new CD and "Public Review" draft.
- then we proceed with the public review, contact people, etc.

Any comments?


Jacques

-----Original Message-----
From: stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] On
Behalf Of Stephen Green
Sent: Thursday, January 15, 2009 3:16 PM
To: TAG TC
Subject: [tag] TestAssertionsGuidelines-draft-0-9-9-9-in-progress-1.doc

The attached file, which I've temporarily called
"0-9-9-9-in-progress-1", seems to me to have all the work we have
completed so far. If we need another 'draft of this draft' prior to any
TC vote we could call it "0-9-9-9-in-progress-2" and so on.

Would we wait until we have decided on a committee draft before asking
Dmitry to check it again (or those parts which have changed since last
time anyway)?

Could this be the draft we vote on whether or not to approve it as a
commitee draft?

I take it it has to go through the process:

committee draft (voted)
Dmitry's checking
any changes
committee draft (voted)
committee spec (voted)
public review spec (voted)
committee spec (if no changes after review)

[if changes after review then
the whole cycle maybe starts again]

Best regards

Steve

--
Stephen D. Green

Document Engineering Services Ltd



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