[sv-ec] No meeting on Monday Feb 28th, next steps

Hi All.
Due to the latest communications from P1800, Johny and Karen, [appended
to this email], we are waiting to hear from the balloting process of
IEEE. 
So, there will no meeting on Monday Feb 28th.

From the timeline given below, I would like to ask all members of sv-ec
to keep Monday April 4th, 2005 open for a possible meeting. [our regular

biweekly meeting would have been on April 11th]. There is a possibility 
that we may need to meet more than once during that week depending on
the 
recommendations from the P1800.  We will plan on going back to our
regular 
meetings once Johny and P1800 communicate the next steps.

thanks,
- Mehdi

====================  Appended Emails ==============================
-----Original Message-----
From: Johny Srouji [mailto:srouji@us.ibm.com] 
Sent: Thursday, February 24, 2005 1:34 PM
To: stuart@sutherland-hdl.com
Cc: 'IEEE1800'; Shalom.Bresticker@freescale.com; 'SV-CC'
Subject: RE: [sv-cc] Re: [P1800] Questions on our activities during the
ballot period.



That's true, but please note (I have double checked w/ Noelle) that
technical committees are 
not allowed to contact the balloters to discuss resolutions, or even
publish resolutions in some 
common area (committee web, minutes, etc) or forum where everyone could
see them, before 
the ballot closes. This is to prevent any inappropriate attempt to
inadvertently influence voters 
while the ballot remains open. 

Even though I understand the need to start the technical work earlier if
possible, in order to balance 
the work load expected and meet our schedule, I am reluctant to starting
the technical issues 
resolutions early. 

Regards, 

--- Johny. 
=============================================
ALSO:
http://www.eda.org/sv-cc/hm/2558.html
http://www.eda.org/sv-cc/hm/2555.html

=======================================================

-----Original Message-----
From: Karen Pieper [mailto:pieper@synopsys.COM] 
Sent: Friday, February 18, 2005 11:45 AM
To: srouji@us.ibm.com; Karen.Pieper@synopsys.COM;
matthew.r.maidment@intel.com; bpierce@synopsys.COM; Mehdi Mohtashemi;
Neil.Korpusik@Sun.COM; chas@cadence.com; Ghassan.Khoory@synopsys.COM;
fhaque@cisco.com; Arif.Samad@synopsys.COM
Subject: Please Read: Schedule for responding to balloting feedback

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