-----Original Message-----
From: Karen Pieper [mailto:pieper@synopsys.COM]
Sent: Monday, November 22, 2004 5:02 PM
To: johny.srouji@intel.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
Cc: bpierce@synopsys.COM; fm@cadence.com
Subject: Update from the P1800 Meeting
Hi, all,
Here is a quick update from the P1800 meeting. All, please read all the way to the bottom of this...
Please continue to work to the December 1 date for completing all "must fix" issues for the revision of the LRM. The schedule is tight, and there is no room to slip the schedule and still make it.
Here are some interesting dates:
12/1 committees are done
12/7 champions meeting for all issues passed by 12/1
12/15 SV-CC is done with datatypes VPI approval
12/15 P1800 approval of the issues passed by 12/1
12/22 SV Champions review datatypes VPI approved issue
1/4-1/9 P1800 conference call to review VPI datatypes changes
1/13 Draft 3 is delivered to the committees
1/21 Committees need to have checked that the edits were incorporated correctly in the draft
Any changes must be approved by the committees
Mid-February Balloting begins
Note here that the SV-CC has an extension of 2 weeks to complete the VPI changes necessary for the datatypes proposal. Also for the SV-CC, the concensus of the P1800 is that reworking the drawings for the VPI into UML is too much risk to the schedule for this release, so please delay that for the next release.
For the SV-BC, please push to finish by 12/1 with high priority: datatypes, bind fixes, and Franciose's friendly amendments to the three issues approved in the latest round. Brad indicated that he has filed an issue on the amendments. The bind fixes have a high priority because Dave Rich indicated that this issue is a show stopper for this revision of the standard.
I've gotten several questions on what we can work on after the 12/1 date. The P1800 encourages each of the committees to continue meeting and addressing errata. When the errata is complete, the committees can also prioritize enhancement work. Please be prepared to review the draft LRMs as they come out and respond quickly. There is not a lot of time in the schedule for this activity and it is important.
Priorities in summary:
1) Support getting the current LRM to and through ballot
2) Continue to work on errata for the next release
3) As time allows, development on enhancements can begin
The sense of the P1800 was that we did not need to file for a new PAR to do this work.
Please let me know if you have any questions,
Karen
Received on Mon Nov 29 09:33:36 2004
This archive was generated by hypermail 2.1.8 : Mon Nov 29 2004 - 09:33:44 PST