[sv-bc] Agenda: April 24 SV-BC Meeting

SV-BC Errata Committee Meeting
Date: Monday, April 24, 2006
Time: 09:00am-11:00am PST

Toll Free Dial In Number: (888)635-9997
International Access/Caller Paid Dial In Number: (763)315-6815
PARTICIPANT CODE: 53904

Agenda

+Review IEEE patent policy
  http://standards.ieee.org/board/pat/pat-slideset.ppt 
  
+ Review Minutes of Previous Meeting

  http://www.eda.org/sv-bc/minutes/sv-bc_06_04_10.txt

+ Issue Review

 Process:
 Identify subset of issues to focus committee effort
 Assign owners for the issues
 Owners bring issues to vote when draft of proposal complete
 Rebuttal to issues should come in the form of specific
  changes to proposal

 Guidelines for issues:
 - Group would prefer not to address issues that complicate merging of
the 
   LRMs or require edits to both specs.  Group would prefer to address
more
   isolated errata until next PAR is set.
 - Try to clarify intent of some issues even if no formal resolution.  
   This would be useful for keeping implementations consistent.
 - Major Severity will be used to identify issues that if not addressed
will
   lead to visibly different implementations
 - Group will use severity to quantify impact of change.
   Issues will be addressed in order of severity.
 - Priority will indicate issue's development progress.  Increase in
priority
   indicates increased progress to proposal and vote.  'Immediate'
priority
   indicates issue is ready for a vote.
 - Individuals will indicate ownership of resolution by adding
themselves
   to the 'assigned to' field.  Karen will help anyone who cannot update
   an issue.
 - Individual members can increase the severity of an issue but the 
   group must agree to decrease severity.
 - Status Filed: Assigned, Resolved & Closed are key states. 


 Actionable Items:

 Per Surrendra (http://www.eda.org/sv-bc/hm/4376.html)

 1051 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001051)
 Recommend to close the issue as it has been discussed and considered 
 previously - " intermediate variables with @* "
 
 1055 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001055)
 Already resolved by SV-BC. Vote to close the issue - "operand/operator
 relationship is ambiguous for event_expressions "

 1056 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001056)
 Already resolved by SV-BC. Vote to close the issue "redundancies in the
BNF"

 1057 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001057)
 Already resolved by SV-BC. Vote to close the issue - " 15.3.2:
$timeskew 
 Case 3 and Case 4 are the same "

 Per Gord (http://www.eda.org/sv-bc/hm/4377.html)
 1272 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001272)
 trivial, immediate
 Issue: Syntax 10-3: &&& should be all red
 Comment: This is a duplicate of 929.  1272 should be closed and 929
should 
          be an email vote.

 1291 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001291)
 feature, immediate
 Issue: range and signedness are parallel attributes of every packed
dimension
 Comment: Brad has suggested that we close this as "won't fix".  I
agree.

 Per Karen (http://www.eda.org/sv-bc/hm/4378.html)
 1127 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001127)	
 Close	Add shared declaration mechanism to Verilog - packages

 Per Shalom (http://www.eda.org/sv-bc/hm/4385.html)
 1125  (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001125)
 I added a proposal to close 1125 as implemented in 1364-2005.
 
 1128  (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001128)
 I added a proposal to close 1128 as implemented in 1800-2005.

 1135 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001135)
 1135 has a proposal to reject and close the issue.


 Volunteers for assignment of major severity items  
 
+ Proposed Next Meeting Date: May 8th

Action Items

Completed

Pending
01/09/2006 Matt assemble issue list for future work
01/09/2006 Matt find owners for future work issues
03/13/2006 Matt Open up SV-BC Issue requesting an index for P1800
03/27/2006 Matt add SVDB 980 to agenda when final draft of 1364-2005 is 
           released
03/27/2006 Cliff post examples demonstrating the need for 0-1 wildcard 
           to justify further action on SVDB 99
04/10/2006 Steven to create proposal for SVDB 1386
04/10/2006 Steven to create proposal for SVDB 1078
04/10/2006 Gord requested to create proposal for SVDB 988

--
Matt Maidment
mmaidmen@ichips.intel.com