| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| --- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Dear reviewers, The editors have completed editing of D3.5. It is now time to review the changes
and report any defects. We have a tight schedule with a deadline of COW Tuesday 27th Jan for you to report defects. The draft for review is D3.5-654, which may be downloaded from the following folder: https://ieee-sa.centraldesktop.com/802-11editorial/folder/4428277/ If you have lost your credentials to centraldesktop, let me know and I’ll resend them. I realize that Matt Fischer and Iwaoka-san do not have credentials. I will send the drafts to them separately, as centraldesktop is currently not letting me add new members. Please report all defects in D3.5 defects reported tab
of the attached spreadsheet and email it to me. (Do not use any other mechanism, such as sending me directly in an email, reporting findings on the D3.5 comments tab., etc…) (The reason I state this is that at every review somebody does something different.) This is a summary of review by CID: (Dorothy is travelling, so I’ll take her CIDs)
The comments to review are in the
“D3.5 comments for review” sheet of the attached spreadsheet. We also have the following non-CID submissions to review:
If anybody cannot perform their review by the deadline, please let me know, and ideally find somebody to substitute asap. And here are essential instructions for the review, which nobody will read, especially the statement about the scope of the review
J How to review approved changes
Process
Download the documents you need for the review. This is typically a version of the draft, a redline version, the approved comment resolutions, and a template for your report on editing
defects. The redline suffers from artefacts resulting from the frame-maker comparison process (see the redline notes at the start of the redline draft). If you find a problem in the redline,
locate it first in the clean draft before reporting it. Fill in any defects you observe in the defects spreadsheet supplied and email your copy of this spreadsheet to your technical editor as soon as you have finished your assignment.
How to report Defects
For each defect fill in a new row of the defect spreadsheet.
The columns of the spreadsheet are:
Please fill in as much data as necessary. But there is no need to slavishly fill in all the fields. Just provide enough detail to make it unambiguous.
If you find yourself spending a lot of time reporting a systematic error, it may save you time to discuss with the editor whether this is actually an issue first.
Please read the Editor’s Notes at the start of the draft. They explain the use of tags and cross-reference styles. These have provoked unnecessary review comments in the past.
Also, please note that when a tag appears in a cross-reference caption (e.g. 7.2 (Ice-cream vendors(#1234)), it will appear as plain (i.e., not green) text. There’s nothing I can do
to change this. Please do not report this as a defect. Goals of the review
The goals of this review are to answer the questions:
·
Did the editor make the changes indicated in the resolution?
·
Did the editor make any non-editorial changes?
o
If you believe that any change is non-editorial, please highlight it. I will ensure that any such comment is brought to motion in TGmb with special notice so that it gets
proper attention.
·
Are the changes introduced by the resolution flagged with the sequence (#1234)? (these are show with a green colour). Is a flag the correct one?
o
Note, some changes are deliberately not flagged, where this is so, this is indicated in the “Edit Notes” field of the comment.
·
(when working on speculative changes only) Sanity check on proposed resolutions.
o
Does it make sense to you?
o
These resolutions will be brought to TGmc for approval. If you disagree with the resolution, by all means discuss with the editor. Any unresolvable disagreements on resolutions
will need to be addressed in that group. Non-Goals
The following is not a goal of the review:
·
To identify new technical bugs in the standard (save them somewhere safe for the next letter ballot). I cannot remedy any such defect as my license as editor does not permit
me to make technical changes except under explicit instruction of the task group.
·
To identify new editorial changes with substantial scope. Anything that is more than a trivial editorial change will need a letter ballot comment.
Best Regards, Adrian P STEPHENS Tel: +44 (1793) 404825 (office) ---------------------------------------------- IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand. SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button. Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________ |
Attachment:
P802.11REVmc D3.5 review.xlsx
Description: P802.11REVmc D3.5 review.xlsx