Re: [sv-champions] RE: [sv-ec] email vote concurrently run for both sv-ec and the champions, ending May 27th

From: Neil Korpusik <Neil.Korpusik_at_.....>
Date: Thu May 28 2009 - 06:00:28 PDT
Hi Shalom,

It looks like I was the source of the error.

I had a copy of the spreadsheet open for a period of weeks. At some
point during this period of time, I had somehow copied the contents of
one cell on top of another, wiping out the original text for ballot
id #55. When I now go back and check any of the 3 spreadsheets that I
have, they all say the same thing that Mehdi had in his.

I will clean up the mantis item and record a bug note mentioning what
happended. That won't be until later today though.


Neil



On 05/28/09 00:59, Bresticker, Shalom wrote:
> Neil,
> 
> I really think a mistake has been made with ballot id #55. Like Steven Sharp, I have recorded that 55 is "Is a class parameter implicitly "public" and "static"?", and I found that it was so recorded also in the xls that Medhi sent out on April 24. This issue is directly addressed by Mantis 2575. 
> 
> I don't know how and when the content of the comment was changed.
> 
> Shalom 
> 
>> -----Original Message-----
>> From: owner-sv-ec@server.eda.org 
>> [mailto:owner-sv-ec@server.eda.org] On Behalf Of Arturo Salz
>> Sent: Thursday, May 28, 2009 10:14 AM
>> To: Neil.Korpusik@Sun.com; sv-champions@eda.org; SV_EC List
>> Subject: RE: [sv-ec] email vote concurrently run for both 
>> sv-ec and the champions, ending May 27th
>>
>>
>> 1.  Mantis 2693
>>
>>     Ballot comment #138: Virtual interface in coverpoint?
>>     Yes _X__ No ___ Abstain ___
>>
>> 2.  Mantis 2598
>>
>> 2.1 Ballot comment #52 How can class type parameters be accessed?
>>
>>     Now handled by Mantis 2575
>>     Close as a duplicate of 2575
>>     Yes _x__ No ___ Abstain ___
>>
>> 2.2 Ballot comment #64 Access to class type parameters
>>
>>     Now handled by Mantis 2575
>>     Close as a duplicate of 2575
>>     Yes _x__ No ___ Abstain ___
>>
>> 3.  Mantis 2575
>>
>> 3.1 Ballot comment #50 Is this.<param_name> or 
>> handle.<param_name> allowed for
>>     class parameters or local parameters of a class?
>>     Yes _x__ No ___ Abstain ___
>>
>> 3.2 Ballot comment #52 How can class type parameters be accessed?
>>     Yes _x__ No ___ Abstain ___
>>
>> 3.3 Ballot comment #55 Related to specification of 
>> hierarchical class methods
>>     for triggerring. Is this limited to only static class 
>> methods or user can
>>     specify object specific method as well. What happens if 
>> the object is not
>>     existing?
>>     Yes ___ No _x__ Abstain ___
>> This is not addressed by Mantis 2575, and it is unclear as to 
>> what the issue is.
>>
>> 3.4 Ballot comment #59 can :: or . be applied to access a 
>> class parameter or a
>>     param declared inside the class?
>>     Yes _x__ No ___ Abstain ___
>>
>> 3.5 Ballot comment #64 Access to class type parameters
>>     Yes _x__ No ___ Abstain ___
>>
>> 4.  Mantis 2608
>>
>>     Ballot Comment #59 :: access and dot access to class 
>> value parameters and
>>     local parameters should be allowed
>>
>>     Now handled by Mantis 2575
>>     Close as a duplicate of 2575
>>     Yes _x__ No ___ Abstain ___
>>
>> 5.  Mantis 2746
>>
>>     Ballot comment #113 "others" coverage bin example
>>     Yes _x__ No ___ Abstain ___
>>
>> 6.  Mantis 2749
>>
>>     Ballot comment #53 class properties and methods are public
>>     Yes _x__ No ___ Abstain ___
>>
>> 7.  Mantis 2750
>>
>>     Ballot comment #121 "expression" should be "constant_expression"
>>     Yes _x__ No ___ Abstain ___
>>
>> 8.  Mantis 2748
>>
>>     Ballot comment #19 Preponed PLI region not included (but 
>> should be removed
>>     from LRM anyway as it does not really exist)
>>     No change required.
>>     See the bug note for an explanation as to why the figure 
>> does not need
>>     to be updated.
>>     Yes _x__ No ___ Abstain ___
>>
>> 9.  Mantis 2745
>>
>>     Ballot comment #111 impicit coverpoint for cross
>>     An enhancement request
>>     Move to "Status=Resolved, Resolution=Open" and add the 
>> following bug note.
>>
>>     "The committee read and considered this feedback. the 
>> committee believes it
>>      is too broad for the scope of the draft to implement at 
>> this time but may
>>      be considered for future revisions."
>>     Yes _x__ No ___ Abstain ___
>>
>>
>>
>> -- 
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>>
>>
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> 
> 

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Thu May 28 06:04:58 2009

This archive was generated by hypermail 2.1.8 : Thu May 28 2009 - 06:05:48 PDT