Re: 1364-2005 intro, index

From: Neil Korpusik (Neil.Korpusik@sun.com)
Date: Mon May 02 2005 - 08:40:37 PDT

  • Next message: Francoise Martinolle: "1364 Ballot Comment Review"

    > When is the final date of submission of the final package to the IEEE
    > approval committee (RevCom, I think)? We have till then to do corrections
    > and additions to the index, and we should, because it is not in such good
    > shape. I did some corrections to the 2001c index, but they were not
    > portable to the 2005 document.

    Below is the latest status on dates that I have received. Based on this
    schedule it looks like we need to have all changes finished by this week.

    The index however might be considered a special case that doesn't need to
    be reviewed and approved. The post-reballoting schedule will be worked
    out at the May 19th P1800 meeting. Karen may have a more definitive
    response on the need date for the updated index.

    Neil

    -------- Original Message --------
    Subject: Balloting Response Schedule is Extended
    Date: Tue, 19 Apr 2005 13:54:18 -0700
    From: Karen Pieper <Karen.Pieper@synopsys.com>
    To: srouji@us.ibm.com, Karen.Pieper@synopsys.com, matthew.r.maidment@intel.com, Brad.Pierce@synopsys.com, Mehdi.Mohtashemi@synopsys.com, Neil.Korpusik@Sun.COM, chas@cadence.com,
    Ghassan.Khoory@synopsys.com, fhaque@cisco.com, Eduard.Cerny@synopsys.com, sv-champions@eda.org

    Hi, Chairs and Champions,

    In the P1800 Meeting today, we discussed the need of the committees for additional time to address issues,
    and developed the following schedule (Note that the official schedule in Dennis's minutes will be posted
    late this evening):

    May 2 Monday Champions meeting (Would 1 to 3pm work for everyone)
                    This meeting is to pass any issues the Committees have addressed, for the May 5 P1800
                    meeting
    May 5 Thursday P1800 meeting 8am to 10am
                    This meeting is to pass any issues so that Stu has more editing time to address these
                    issues
    May 9 Monday Champions meeting (How about 9am to 11am for this one?)
                    The Committees need to be complete with their changes by this meeting. The SV-CC will
                    have a few days to cope with issues raised by this meeting
    May 11 Wednesday Champions meeting (How about 10am to 11am for this one?)
                    This meeting is to make recommendations on whatever "fallout" issues for the SV-CC there
                    were from the May 9 meeting
    May 19 Thursday P1800 meeting
                    This meeting will ratify the last of the changes for the reballot draft. We should also
                    have the ballot spreadsheet responses updated and available for ratification.
    May 24 The draft of the LRM with all of the changes incorporated will be available for final review
    May 27 Comments on the May 24th draft are due to Stu
    May 31 The Balloting LRM is ready
    June 2 P1800 meeting to send the balloting draft back to reballot
            Reballoting will take 10 days, we will work out the post reballoting schedule on May 19.

    As you can see, we were able to give each of the committees a few more weeks to address the issues on their
    lists. Please continue to address issues for the earlier P1800 meetings as that will allow more time for
    Stu to complete the editing.

    The P1800 really appreciates that hard work that everyone has been doing, and commented on it several
    times during the meeting.

    Thanks all,

    Karen 

    -- 
---------------------------------------------------------------------
Neil Korpusik                                     Tel: 408-720-4852
Staff Engineer                                    Fax: 408-720-4850
Frontend Technologies - ASICs & Processors (FTAP)
Sun Microsystems
email: neil.korpusik@sun.com
---------------------------------------------------------------------

    This archive was generated by hypermail 2.1.4 : Mon May 02 2005 - 08:16:26 PDT and
    sponsored by Boyd Technology, Inc.