ARC Fasttrack Handbook

ARC Participant Duties - Running ARC Fasttracks

This describes the Sun-Internal process which is not usable off-SWAN

Background Information

This document contains the procedure for an ARC member, intern, or licensee to follow when sponsoring a fast-track before an ARC.

Instructions for a project team that wants their ARC case reviewed by fast-track are in Fasttrack Process FAQ.

Fast-Track Steps

• Find or Get a Case Number

  If the one-pager was submitted, but has not yet been assigned to an ARC, it may yet be in the project catalog, but in a "holding area" known to sac_find. Use the white search box on the sac web site to type in a name or keyword that you believe uniquely identifies the one-pager.

  The one-pager will be shown with "??ARC" (rather than PSARC or LSARC) if it has not yet been assigned to an ARC. Select the ARC you deem most appropriate to review the fast-track.

  If no one-pager was submmitted to the one-pager email alias, use sac_nextcase to get a case number. If you encounter "permission denied" errors while running the script it may be because you aren't in the sac group. Check for your login with "ypmatch sac group" or "nismatch sac group". If sac_nextcase is successful, it will create a subdirectory under the named ARC whose name is the case number, such as /shared/sac/arc/PSARC/1995/012.

• Create the Case's IAM.* File
  If needed, copy /shared/sac/arc/ARC-Templates/IAM.proto into that case directory, rename it to reflect the case's title, and edit its contents. The "Name" field's value should be in title format; that is, all major words in it should start with capital letters. Make sure the "Status" field's value matches one of the regular expressions given in /shared/sac/Tools/lib/status.re. For fast-tracks, it should be "waiting fast-track mm/dd/yyyy". The date should be that of the fast track's expiration, not the time it was submitted; the standard expiration period is one week from date of submission. You should edit the "Owner" field to name yourself. Assure the IAM* file has permissions 664 and group "sac".

  Mail addressed to ??arc (e.g., psarc) that mentions the case number in its subject line will automatically be appended to the "mail" file in the case directory. If there is correspondence that predates the directory's creation, you should seed the mail file with it.

• Create the Case's "materials" Subdirectory
• Send Announcement Mail
  Make sure you've discussed the proposed commitment levels with the project team, and include this information in the message. Also, make sure that you have discussed the proposed delivery vehicle (major, minor, micro, or patch release), and include this information in the message, as well. Projects wishing to deliver into a Solaris Update must obtain ARC approval for delivery into a patch release.

  If you're aware of any potential issues with the proposal, state them in the prefatory material. If the case materials aren't overly bulky, include them at the end of the message; otherwise, include a pointer to them.

• Attend the Next ARC Meeting
• Close the Case When It Is Approved
  The case file should also include the final description or specification of the proposal that was approved, since the proposal may have been revised due to ARC discussion. The fast-track owner is responsible for making sure the final specification in the case directory accurately describes the approved proposal. Before approval, this can serve as the "current proposal" -- so the current thoughts need not be inferred from the mail archive. After approval, it takes the place of the opinion, documenting in one place exactly what was approved (e.g., for PRA audit).