[sv-bc] Mantis upgrade

Hello all eda.org mantis users, (P1800, P1081, OVL, and VerilogAMS)

 

I volunteered to upgrade the Mantis site for the P1800 WG recently and I
am ready to turn it loose. The current version we are using is a
pre-release over 3 years old. The latest version has much better search
mechanisms as well as better user and system level customizations.  The
mantis system will be down for about a half an hour during the upgrade
while the old system is being backed up and converted over to the
system. I plan to do this sometime on Wednesday June 6th.

 

Some of the useful improvements in the latest Mantis system are:

*	Faster search times
*	Much more advanced search criteria, like the ability to have
multiple selections for a field, and most fields are now selectable
*	Ability to save commonly used search filters
*	A 'relationship' field so instead of adding a bugnote that says
this bug is related to or depends on Mantis XXXX, you can add that
information in a field for that purpose

 

As part of the upgrade, I have made a few changes that have been
reviewed by the champions committee and the various technical committee
(TC) chairs. These changes affect the status of a mantis issue after it
has been approved by the WG and will give users a better way to filter
issues that have been approved by each TC. The changes also give the  TC
chairs better control over the progression of an issue by enforcing our
agreed upon process as a result of encoding them into a Mantis state
machine.  I have attached an updated copy of the SV database operating
procedures.

 

In a nutshell, the SV-LRM category has been eliminated and a new set of
statuses have been created to represent the issue while it is in the
editors hands. The effectual change the average user will see is when
the editor has finished their edits; the ACKNOWLEDGED status is now the
COMPLETED status. If there is problem with the edits, the user will just
change the status to EDITOR instead of changing the category to SV-LRM
and status to NEW. If the editor needs more information, the status will
be changed to REVIEW instead of changing the status to NEW and the
category back to SV-*. With these changes, the category now remains
undisturbed throughout the process.

 

The typical flow for an issue requiring an LRM change is

 

NEW -> ASSIGNED -> RESOLVED -> APPROVED -> COMPLETED -> CLOSED

 

The typical flow for an issue not requiring an LRM change is

 

NEW -> ASSIGNED -> RESOLVED -> CLOSED

 

The typical flow for an issue requiring an LRM change that is
incorrectly applied is

 

NEW -> ASSIGNED -> RESOLVED -> APPROVED -> COMPLETED -> EDITOR->
COMPLETED -> CLOSED

 

 

The complete state machine is shown below (read the attachment for a
complete description)

 

 

 
+------------------------------------------------------+ 

                       |           +----------+---------+----------+
|             

                       |           |          |         |          |
|

                       ^           ^          V         ^          V
V

NEW -> ASSIGNED -> RESOLVED -> APPROVED -> REVIEW -> EDITOR -> COMPLETED
-> CLOSED

 ^        ^            V                                ^          V

 |        |            |                                |          |

 +--------+--FEEDBACK--+                                +----------+

 

Thanks,

 

Dave

 

 

David Rich
Verification Technologist
Design Verification & Test Division
Mentor Graphics Corporation
dave_rich@mentor.com
Office:   408 487-7206
Cell:     510 589-2625

 


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