[sv-champions] Mantis upgrade

Hi eda.org mantis managers, (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. You
can see a trial version of the upgrade at
http://www.eda-stds.org/~daver/mantis/. E-mail notifications have been
turned off, so feel free to experiment with adding and modifying issues
without pestering anyone.  I will test the e-mail notification system
just prior to switching over. I plan to take the do the final swap on or
about June 1st.

 

As part of the upgrade, I have made a few changes in agreement with the
various technical chairs 

 

The current version has a fixed set of statuses (NEW, ASSIGNED,
FEEDBACK, RESOLVED, ACKNOWLEDGED, CONFIRMED, CLOSED) and a fixed idea of
a progression through those statuses. The new version lets you customize
all that. The change that I have made is to match the process we use in
the Accellera/IEEE - t hat is technical committee resolution, followed
by Working Group approval, and finally implementation in the LRM (or
library).  I have worked with all the technical chairs in getting
agreement for a new set of statuses

 

The biggest change for the SV committees is that the old ACKNOWLEDGED
status is now called APPROVED and there is no longer a need to move in
and out of a separate SV-LRM category.  Once an issue has been APPROVED,
there is no going back to an earlier status, and the category (e,g
SV-BC) is undisturbed in the process. There is no change to the process
prior to WG approval

 

The statuses I propose are as follows (you can ignore the numeric codes
10, 20, 30, etc, except that codes over 60 are read-only - no updates
are allowed)

 

<?php

# status

define( 'NEW_',      10 );   # NEW seems to be a reserved keyword

define( 'FEEDBACK',  20 );   # Committee/WG needs more information

define( 'EDITOR',    30 );   # Incomplete/Action item for editor

define( 'REVIEW',    40 );   # Editor needs more information

define( 'ASSIGNED',  50 );   # Work in progress

define( 'RESOLVED',  70 );   # Committee has passed proposal

define( 'APPROVED',  80 );   # WG has approved issue for LRM

define( 'COMPLETED', 60 );   # Editor has completed edits in draft

define( 'CLOSED',    90 );   # No Further action

?>

 

The typical flow is

 

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

 

Feedback is now just used prior to approval, as it was previously but
now I have separate status for loops with the editor. Some other
possible flows

 

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

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

                       |           |          |         |          |
|

                       ^           ^          V         ^          V
V

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

 ^        ^            V                                ^          V

 |        |            |                                |          |

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

 

The complete state machine, which defines the allowed status
transitions, is shown in this table:

 

# Current state                    = allowed next states

$g_status_enum_workflow[NEW_]
='20:feedback,30:editor,50:assigned,70:resolved,30:editor';

$g_status_enum_workflow[ASSIGNED]  ='10:new,20:feedback,70:resolved';

$g_status_enum_workflow[FEEDBACK]  ='10:new,50:assigned,70:resolved';

$g_status_enum_workflow[RESOLVED]  ='20:feedback,80:approved,90:closed';

$g_status_enum_workflow[APPROVED]  ='40:review,60:completed';

$g_status_enum_workflow[COMPLETED] ='30:editor,90:closed';

$g_status_enum_workflow[EDITOR]    ='40:review,60:completed,90:closed';

$g_status_enum_workflow[REVIEW]    ='30:editor,90:closed';

$g_status_enum_workflow[CLOSED]    ='50:assigned';

 

 

Some statuses can only be entered by a manager, and a manger has
privileges to write to an issue even if it is in a read-only status.



Please give the new system a try. I would like to do the transfer within
two weeks (before I have to re-learn how to do the translation:-)).

 

The URL is  http://www.eda-stds.org/~daver/mantis/

 

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.