Hi Neil,
I should have set 'version fixed' manually. What is the current value? Yes, I did first assigned this issue to myself. I see now that it is possible to move the set a new issue directly to Editor status.
Thanks,
Dmitry
-----Original Message-----
From: Neil Korpusik [mailto:neil.korpusik@oracle.com]
Sent: Thursday, May 12, 2011 01:55
To: Korchemny, Dmitry
Cc: 'sv-ac@eda-stds.org'
Subject: Re: [sv-ac] Editorial issues
Hi Dmitry,
The 'version fixed' and 'product version' fields are not right.
They must be getting set automatically. You didn't set these
did you? Other than that, everything else looks good.
I thought you would be able to go directly from 'new' to 'editor'.
When you assigned it to yourself, that must be what forced you
to have to go through all of the intermediate states before
being able to get to the editor state. I checked the "workflow
transitions" and that is what happened. You should have just
gone from new to editor.
Neil
On 05/11/11 14:06, Korchemny, Dmitry wrote:
> Hi Neil,
>
> I opened Mantis 3556 and set its status to Editor (it took me a while to move it around through all the preceding statuses). Let me know if I understood you correctly.
>
> Thanks,
> Dmitry
>
> -----Original Message-----
> From: Neil Korpusik [mailto:neil.korpusik@oracle.com]
> Sent: Wednesday, May 11, 2011 23:39
> To: Korchemny, Dmitry
> Cc: 'sv-ac@eda-stds.org'
> Subject: Re: [sv-ac] Editorial issues
>
> Hi Dmitry,
>
> Ok, I thought you were referring to existing mantis items.
>
> Mantis 3232 is a parent mantis item for small editorial issues.
>
> In the past we have sent purely editorial issues directly to the Editor, but
> what you are suggesting sounds like a better approach. Opening a new mantis
> item with a set of Editorial issues in it would provide a record of those
> changes. The existing SystemVerilog process flow diagram allows for this type
> of mantis item to be created.
>
> Note that the Editor has the right to refuse to make any changes sent directly
> to him that he determines are not purely Editorial in nature. The process
> flow doesn't allow you to change a mantis item when it is in the Editor status.
> You would need to open another mantis item if you find more Editorial issues
> at a later point in time. Going through the normal mantis approval process
> relieves the Editor from having to make a judgment call as to whether it is
> a purely editorial.
>
> If you choose to open a mantis item for purely editorial issues, please use
> the following settings. Make this mantis item a child of mantis 3232. Add a
> note to the new mantis item explaining that it is an Editorial issue.
> Attaching a proposal that puts the suggested change into context should be
> provided. That helps ensure the change is made properly.
>
> Status: editor
> Severity: trivial
> Type: errata
>
>
> Neil
>
>
>
> On 05/11/11 12:48, Korchemny, Dmitry wrote:
>> Hi Neil,
>>
>> I found an editorial issue in the text not affected by any new Mantis. What should I do?
>>
>> Thanks,
>> Dmitry
>>
>> -----Original Message-----
>> From: Neil Korpusik [mailto:neil.korpusik@oracle.com]
>> Sent: Wednesday, May 11, 2011 22:47
>> To: Korchemny, Dmitry
>> Cc: 'sv-ac@eda-stds.org'
>> Subject: Re: [sv-ac] Editorial issues
>>
>> Hi Dmitry,
>>
>> Below is what I had in my previous email. This is the process
>> we should follow. We don't create new mantis items for this,
>> we make updates to the existing mantis items.
>>
>> ------
>>
>> All of the mantis items that currently have their status set to
>> Completed will need to be reviewed for accuracy. The following process
>> should be used.
>>
>> 1. When a problem is found with the updates made by the editor
>>
>> -- The mantis status should be set to Editor.
>> -- A note should be added to the mantis item which explains the problem.
>>
>> 2. When the changes made by the editor are correct
>>
>> -- The mantis status should be set to Closed.
>> -- A note should be added mentioning that the updates were made correctly.
>>
>>
>>
>> Neil
>>
>>
>>
>>
>>
>> On 05/11/11 12:37, Korchemny, Dmitry wrote:
>>> Hi Neil,
>>>
>>>
>>>
>>> Is the committee authorized to open a new editorial issue and to set it
>>> to Editor status instead of Resolved? Otherwise, the new editorial
>>> issues won't be fixed in this draft.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Dmitry
>>>
>>> ---------------------------------------------------------------------
>>> 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* <http://www.mailscanner.info/>, 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.
>>
> ---------------------------------------------------------------------
> 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.
>
---------------------------------------------------------------------
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 Wed May 11 22:50:51 2011
This archive was generated by hypermail 2.1.8 : Wed May 11 2011 - 22:50:56 PDT