Re: [P1800] 25 March 2010 IEEE P1800 Study Group Continuation Meeting Minutes

Hi Dennis, Karen,

I have a question on the following line from the minutes:

    "The committees are authorized to approve FIX, CLOSE and DUPLICATE errata items."

My question is specific to the part about a TC being allowed to close errata.
The process that we use for mantis items doesn't allow any mantis item to be
closed until the resolution approved by the TC has also been approved by
the Champions and the Working Group. I assume that what was meant by this
statement in the minutes, where it refers to closing a mantis items, meant to
say that the TCs are allowed to approve a resolution of "no change required" or
"won't fix", along with the other resolutions of "duplicate" and "fixed" that
you have already listed.

Another way to say it is that the TCs are allowed to "resolve" mantis items.
That covers a set of different resolutions.

This needs to be clarified for the work that the TCs are about to begin.

Neil

On 03/26/10 15:50, Brophy, Dennis wrote:
> *IEEE P1800 SystemVerilog Study Group*
>
> *UNAPPROVED MINUTES*
>
> *25 March 2010 Continuation of 11 March 2010 *
>
> *8:00 a.m. – 10:00 a.m. PDT*
>
> *Teleconference*
>
>
>
>
> *1 CALL TO ORDER - INTRODUCTIONS & AFFILIATIONS*
>
> The meeting resumed at 8:02 a.m. PDT with the following present:
>
>
>
> *_Member DRs/DRAs Present: _*
>
> Dennis Brophy (Mentor Graphics, DR)
>
> Mehdi Mohtashemi (Synopsys, DR)
>
> Karen Pieper (Accellera, DR)
>
> Daniel Even-haim (Intel DR)
>
> Matt Maidment (Intel, DR)
>
> Charles Dawson (Cadence, DR)
>
> John Havlicek (Freescale, DR)
>
> * *
>
> *_Member DRAs Present:_*
>
> Yatin Trivedi (Synopsys DRA)
>
> Brad Pierce (Synopsys DRA)
>
> Dave Rich (Mentor Graphics DRA)
>
> Stephen Boyd (Cadence, DRA)
>
> Ghassan Khoory (Synopsys, DRA)
>
>
>
> *_Observers:_*
>
> Nikhil Rishiyur (Bluespec)
>
> Shalom Bresticker (Intel)
>
> Scott Little (Freescale)
>
> Neil S (Marvell)
>
> Michiel Ligthart (Verific Design Automation)
>
> JL Gray (Verilab)
>
> * *
>
> *9 Discussion of new PAR *
>
> The SystemVerilog Working Group completed the details of the PAR form to
> be entered into the IEEE SA project authorization management system.
> Click here
> <http://www.eda-twiki.org/svdb/file_download.php?file_id=4261&type=bug> for
> the details that will be entered by Chair Pieper.
>
> A motion (Dennis Brophy, John Havlicek) was made to approve the PAR for
> submittal to the DASC. The motion passed unanimously.
>
> *10 P1800 technical committees and Champions operational update *
>
> Discussions on getting the technical committees started again resumed
> from the suspended meeting. The committees should be technical work on
> errata and clarifications. And enhancements motivated by the
> requirements gathering meeting should be taken into account as well.
> Any work the subcommittee do will not be officially approved until after
> the PAR is approved and the Working Group are formed.
>
> A motion (Dennis Brophy, Matt Maidment) was made to authorize the
> subcommittees to develop a list of the top-25 errata, enhancements and
> clarification issues or categories taking in to consideration the
> feedback from the requirements gathering meeting. The creation of this
> list is to be completed by 13 May 2010. The committees are authorized
> to approve FIX, CLOSE and DUPLICATE errata items. The motion passed
> with one dissent. (Cadence is recorded as voting against the motion.)
>
> The subcommittees can now on or after the following times: SV-BC Monday
> 9 a.m. – 11 a.m. PDT, SV-EC 11 a.m. – 1 p.m. PDT starting on the 12^
> April 2010 and the SV-CC can start meeting on Wednesday, 14 April 2010.
>
> *12 Next meeting (announce date, time, and location, if known) *
>
> * April 8, 2010 P1800 Meeting teleconference 8:00 a.m. – 10:00 a.m. PDT
>
> *13 Adjournment *
>
> A motion (Mehdi Mohtashemi) was made to adjourn the meeting. The end of
> the agenda being reached, no second was needed and the meeting adjourned
> at 9:15 a.m. PDT.
>
>
>
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.