Reviewing the file "status.allowed" for guidance on how to update
the IAM file for a case, it seems to stop being useful once a case
gets to the opinion review stage. Below is a proposed patch to the
"status.allowed" file to make it more complete.
Darren
------- status.allowed -------
*** /tmp/sccs.eLaGny Wed Sep 9 11:32:22 2009
--- status.allowed Wed Sep 9 11:32:00 2009
***************
*** 119,124 ****
--- 119,126 ----
waiting need spec( MM/DD/YYYY)?
waiting need vote MM/DD/YYYY
waiting need( draft)? opinion( MM/DD/YYYY)?
+ # when the opinion is ready to be submitted, see the
comments
+ # below for "waiting PSARC review".
waiting ALL review MM/DD/YYYY
# Covers both ... *ARC... as well as ... SAC... review
cycles
closed approved MM/DD/YYYY
***************
*** 154,156 ****
--- 156,181 ----
closed grandfathered
closed hole
# Unknown...
+
+ waiting PSARC review MM/DD/YYYY
+ # a minium of 7 days is required for the review by PSARC
+ # of an opinion submitted. The opinion should be sent by
+ # email to PSARC. If written using the nroff template,
+ # use nroffit to format the opinion appropriately.
+ # After allowing time for PSARC review and including any
+ # feedback, it is then eligable for SAC review.
+ waiting SAC review MM/DD/YYYY
+ # a minium of 7 days is required for the review by SAC
+ # of an opinion submitted. The opinion should be sent by
+ # email to sac-review at sac.
+ # a minium of 7 days is required for the review by the SAC
+ # of an opinion submitted. The opinion should be sent by
+ # email to sac-review at sac.
+ # After allowing time for SAC review and including any
+ # feedback, it is then eligable for SAC review.
+ closed approved MM/DD/YYYY
+ # After the integration of feedback from the members is
+ # complete, the opinion is then sent to sac-opinion at sac
+ # for archiving and to the relevant steering committee(s)
+ # (<steeringcommittee>-opinion at scs.eng -- for Solaris
+ # Foundation Steering Committee, it's sfsc-opinion at scs.eng).
