[sv-cc] [Fwd: Please Read: Schedule for responding to balloting feedback]

From: Charles Dawson <chas_at_.....>
Date: Wed Feb 23 2005 - 09:37:02 PST
-------- Original Message --------
Subject: Please Read: Schedule for responding to balloting feedback
Date: Fri, 18 Feb 2005 11:45:24 -0800
From: Karen Pieper <Karen.Pieper@synopsys.com>
To: srouji@us.ibm.com, <Karen.Pieper@synopsys.com>,
<matthew.r.maidment@intel.com>, Brad.Pierce@synopsys.com,
Mehdi.Mohtashemi@synopsys.com, <Neil.Korpusik@sun.com>, chas,
<Ghassan.Khoory@synopsys.com>, <fhaque@cisco.com>, <Arif.Samad@synopsys.com>



Hi, SV-* Chairs and Co-chairs,

         After yesterday's P1800 meeting, I can now communicate the
process for work in the P1800 SV-* committees going forward.  Please
note that the schedule is very tight, and that there are some suggested
all day Face-to-Face meetings that need to be scheduled below.

February 22:    The balloting process opens.  As feedback is filed with
the IEEE, it will be forwarded
         to Johny, and he is likely to forward it on to me and the
Champions for preliminary processing
         into buckets (see March 28 below).

         The committees may wish to leave open the opportunity to meet in
this time in case some
         feedback is forwarded to the committee; however, the committees
are NOT         AUTHORIZED to discuss any issue not raised in the ballot
feedback
         forwarded from the Champions until further notice.  Please
update your
         committee agendas as required.

March 24:       The ballot closes.

March 28:       P1800 will receive the accumulated feedback filed with
the balloting.
         This feedback will be given to the Champions to sort into
several buckets:

         1)  Issues that may require substantive changes to the LRM are
forwarded to the SV-* committees
         2)  Issues that are editorial changes will be forwarded to Stu
         3)  Issues that are "not a bug" are commented on appropriately
and passed back to the P1800

         The P1800 recommends that the champions have a face-to-face all
day meeting to complete
         this process.

March 31:  The Champions are complete with their initial classification
and assignment of issues to
         committees.

         The P1800 recommends that the SV-* committees plan an all day
face-to-face to deal with the
         issues raised.  Possible resolutions are:

         1)  Changes are made to the LRM to address the issue
         2)  Addressing the issue is determined to decrease consensus in
the committee is so noted on
                 the issues spreadsheet.
         3)  Other determination of the issue is made and is also so
noted in the issues spreadsheet
                 Note:  Saying that an issue will be delayed to a future
release is not an allowed response.

April 12:  The committees are complete with their LRM updates and issue
spreadsheet updates.

         The Champions will meet, do their review of LRM changes looking
for inconsistency, etc.
         This is likely to be a phone meeting.

April 15:  The Champions have completed their analysis and the data is
forwarded to the P1800.

April 19:  The P1800 has a WG meeting in Austin to approve the changes
and responses.

May 3:  The updated draft is ready for editorial review of the changes

May 9:  The re-ballot draft is complete

May 10:  Voting on the re-ballot draft starts.

Please let me know if you have any questions or concerns.

Karen


-- 
Charles Dawson
Senior Engineering Manager
NC-Verilog Team
Cadence Design Systems, Inc.
270 Billerica Road
Chelmsford, MA  01824
(978) 262 - 6273
chas@cadence.com
Received on Wed Feb 23 09:37:07 2005

This archive was generated by hypermail 2.1.8 : Wed Feb 23 2005 - 09:37:21 PST