[sv-bc] SV-BC Draft LRM Review Process Per Jan 17 CC

Hi All.

For those SV-BC members who did not attend the Jan 17 SV-BC meeting,
especially those who were assigned and helped resolved issues for
the upcoming draft of the LRM I want to explicitly highlight the process

to which the committee has agreed for closing on the review.

(This can also be found in the Jan 17 meeting minutes
http://www.eda.org/sv-bc/minutes/sv-bc_05_01_17.txt)

+Update on LRM Draft & Review Process

The LRM draft is done but needs to be secured prior to distribution.
Securing & distributing should happen any day. The timeline is for the
sv-bc to complete its review by Jan 24, end of day. The overall goal
is to have any issues resolved in time for the Jan 26 P1800 meeting.

The mechanics of the review process are:

   Once an issue has status:acknowledged, the appropriate SV-* committee

   must review the LRM to ensure that changes for correctness.
     a. If the change is correct, the issue is moved to status:closed
     b. If the change is not correct and the description was correct,
the
         issue is moved to category:SV-LRM and status:new, and mail is
sent
         to the LRM team
     c. If the change is not correct and the description of the change
         needs to be modified, the issue is changed to status:assigned

In addition the sv-bc agreed that:

  For each sv-bc issue the assignee should be the one to review the LRM
to
  ensure the change is correct and to update the status accordingly in
the
  SVDB.

  For issues whose changes were determined the sv-bc committee to be
  non-trivial, one or more additional reviewers were identified. The
  additional reviewer(s) will report the status of their review(s) to
the
  issue assignee. The issue assignee should wait for all of the
additional
  reviewer(s) before updating the status of their issue(s).

  For those assignees who were absent from today's meeting, a secondary
  reviewer was assigned to review and potentially update the status
  in the event the issue assignee is not available. Unless specifically

  noted otherwise below, Brad agreed to review issues assigned to Dave
Rich
  and Nikhil, and Matt agreed to review issues assigned to Doug Warmke.

  Here is the list of Issues/Additional Reviewer(s) for Non-Trivial
Changes

  012 - Dan
  020 - Dan
  021 - Steven
  034 - Dan
  038 - Brad
  039 - Dave
  051 - Francoise
  074 - Brad
  076 - Surrendra
  091 - Dan
  110 - Steven
  111 - Brad
  115 - Mark
  163 - Brad
  164 - Dan
  168 - Kathy, Matt, Steven
  213 - Brad
  216 - Brad
  218 - Steven
  226 - Steven
  254 - Surrendra
  272 - Brad
  273 - Matt
  276 - Karen
  291 - Brad
  302 - Matt
  315 - Mark
  321 - Matt
  322 - Dan
  323 - Dan
  327 - Matt
  328 - Matt

  The sv-bc identified LRM sections relevant to the committee that are
to
  be reviewed on a more holistic basis by the committee. Below is the
list
  of relevant sections & corresponding reviewers:

  01/Introduction - Karen
  02/Literals - Steven
  03/Data Types - Surrendra
  04/Arrays - Brad
  05/Data Declarations - Don
  07/Operators & Expressions - Francoise
  08/Statements - Brad
  10/Tasks & Functions - Brad
  18/Hierarchy - Kathy
  19/Interfaces - Karen
  21/Parameters - Brad
  22/Configurations - Mark
  23/System Tasks & Functions - Matt
  24/VCD - Steven
  25/Compiler Directives - Don
  Annexes - Brad

  The reviewers agreed to send email to reflector by Jan 24
acknowledging
  completion.

NOTE: Please send mail to the reflector with any issue not logged in the
SVDB.

Thanks to all of you for your cooperation!

Matt

--
Matt Maidment
mmaidmen@ichips.intel.com