Re: [Fwd: errata/123: PROPOSAL - Fwd: identifier and indexing syntax]

From: Shalom.Bresticker@motorola.com
Date: Wed Feb 19 2003 - 19:48:13 PST

  • Next message: Karen Pieper: "Cancelling Monday's meeting"

    Precedence: bulk

    I am going back to the army this morning probably for 4 days.
    It will have to wait for next week.
    If you are going to dvcon, then look for it when you return.

    One immediate comment: in the proposal for 140, the table of examples at the end
    should be in <pre> format. Otherwise, it is unreadable.

    Shalom

    On Wed, 19 Feb 2003, Stefen Boyd wrote:

    > Date: Wed, 19 Feb 2003 19:08:00 -0800
    > From: Stefen Boyd <stefen@boyd.com>
    > To: Shalom Bresticker <Shalom.Bresticker@motorola.com>
    > Cc: etf@boyd.com
    > Subject: Re: [Fwd: errata/123: PROPOSAL - Fwd: identifier and indexing syntax]
    >
    > Shalom,
    >
    > Last meeting I wasn't able to stay on top of changes to
    > the proposals as well... ideally, what is there can stay
    > unchanged. Comments below:
    >
    > At 03:39 PM 2/19/2003 +0200, Shalom Bresticker wrote:
    > >#123 was passed by etf, but the proposal in the fix field of the database is
    > >still wrong.
    >
    > Can you point me to the correct version that was passed? I didn't
    > see anything in the minutes that suggested that it was changed before
    > passing.
    >
    > >There are other etfpassed issues in which the fix field also requires editing,
    > >such as deletion of now irrelevant comments, or omission of what is being
    > >changed.
    >
    > Please let me know when you see ones needing revision. I generally
    > try to eliminate the extra stuff on ones passed during meetings, but
    > may not get all of it out of email voted issues (there is always the
    > VSG to fix this before it gets vsgpassed).
    >
    > >Also, in cases where we make some changes but not others (e.g., because it is
    > >dealt with
    > >in another issue), we should note it in the fix field as well, The 'fix' field
    > >is essentially a 'resolution' field.
    > >
    > >The reader should be able to find a resolution of each comment in the bug
    > >submission in the fix field.
    >
    > I agree that it is the final say on how issue was handled. I have
    > taken the tact that if part of the issue wasn't handled in the fix,
    > it was deliberate and didn't need a note. If there are ones where you
    > would like a reference, bring it up. If it's important, these notes
    > should be part of the proposal.
    >
    > Stefen
    >
    >
    >
    > --------------------
    > Stefen Boyd Boyd Technology, Inc.
    > stefen@BoydTechInc.com (408)739-BOYD
    > www.BoydTechInc.com (408)739-1402 (fax)
    >

    This archive was generated by hypermail 2.1.4 : Wed Feb 19 2003 - 19:49:16 PST and
    sponsored by Boyd Technology, Inc.