integrationident	"@(#)rtitool.info	1.28	96/07/26 SMI"
#
# Copyright (c) 1994 by Sun Microsystems, Inc.
#

##################################################
#
# Main Panel Window
#
##################################################
:main_general
Main Panel

Provides functions common to all templates.
##################################################
:main_file
File

Provides these options:

Save to file	Opens the Save To File window.

Send		Sends the RTI mail message to the
		addresses in the Mail To: and Mail
		Cc: text fields.

Print		Submits a copy of the RTI mail
		message to the printer using the
		print command listed in the
		general properties.

##################################################
:main_view
View

Provides these options:

Show		Opens the Show window which
		displays the RTI mail message.

Error Log	Opens the Error Log window.
##################################################
:main_props
Props

Opens the Properties window.
##################################################
:main_template
Template

Provides these options:

Implementor	Display the Implementor Template

Evaluator	Display the Evaluator Template

Patch           Display the Patch Template
##################################################
:main_reset
Reset

Provides these options:

Clear all fields and load default values
	Reset all fields to their default value
	defined either in the properties or
	system configuration file.

Clear all fields
	Reset all fields to blank or no value.
##################################################
:main_help
Help

Provides these options:

Send Feedback	Opens the feedback window.

General Help	Displays a pullright menu with
		selections of help about rtitool.
##################################################
:main_send
Send

Sends the RTI mail message to the addresses in
the Mail To: and Mail Cc: text fields.
##################################################
:main_show
Show

Opens the Show window which displays the RTI mail
message.
##################################################
:main_check
Check

Checks that all the required fields for the RTI
have been filled in.  Errors are displayed in the
Error Log window.
##################################################
:main_query
Query

Opens the Query window.
##################################################

##################################################
#
# Save Window
#
##################################################
:save_general
Save Popup

Allows you to save the RTI message to a file.
##################################################
:save_file
File to save to

Path to save the RTI message to.  Defaults to
your "RTI Log Directory" defined in props and
the file name rtifile.txt.
##################################################
:save_save
Save

Save the RTI message to the path given in "File
to save to".
##################################################
:save_cancel
Cancel

Cancel the save.  Dismisses the window.
##################################################

##################################################
#
# Props Window (Generic)
#
##################################################
:props_generic_general
Properties

Allows you to set properties related to rtitool
or to the specific templates.
##################################################
:props_generic_cat
Category

General		Display the General props sheet.

Implementor	Display the Implementor props
		sheet.

Evaluator	Display the Evaluator props sheet.

Patch		Display the Patch props sheet.
##################################################
:props_generic_sysdefs
System Defaults

Load the system default values into the current
props sheet.
##################################################
:props_generic_apply
Apply

Make the values for the current prop sheet active
and save them to your ~/.rtitoolrc file.  The
new values will not be displayed in the RTI
template windows until you select Reset.
##################################################
:props_generic_reset
Reset

Load the currently defined  values into the
displayed prop sheet.

Current values are a combination of the values
from you .rtitoolrc and system configurations
files.  Values from your .rtitoolrc take prece-
dence over the system defaults.
##################################################
:props_generic_mailto
Mail To

The email address of where to send the RTI
message.  This must be a valid address to the
rtiroute software.
##################################################
:props_generic_mailcc
Mail Cc

The email address of where to send a copy of the
RTI message.
##################################################

##################################################
#
# General Props Window
#
##################################################
:props_gen_general
General Props Sheet

Allows you to set properties related to rtitool
or general to all templates.
##################################################
:props_gen_start
Starting Template

Implementor	Show the Implementor template on
		start up.

Evaluator	Show the Evaluator template on
		start up.

Patch		Show the Patch template on start
		up.
##################################################
:props_gen_dsquery
Bugtraq+ Server Name

The value for the Sybase DSQUERY environment 
variable, indicating which bugtraq+ database to
use.  By default, this should be set to the 
live database, BUGTRAQ.  In situations where 
BUGTRAQ is down, this value might be temporarily 
changed to BUGRPT, the readonly replicated database.
##################################################
:props_gen_log
RTI Log

Turn on/off RTI logging.  If logging is enabled,
copies of the RTI mail messages will be saved
in mailbox format to the path defined by the
"RTI Log Directory" and "File".
##################################################
:props_gen_logdir
RTI Log Directory

The directory to log RTI mail messages.
##################################################
:props_gen_logfile
(RTI Log) File

The name of the file in the RTI log directory to
save copies of RTI mail messages.
##################################################
:props_gen_prtcmd
Print Command

The command used to print RTI mail messages.
The text of the mail message is piped to the
STDIN of the command.
##################################################

##################################################
#
# Query Window
#
##################################################
:query_general
Query Popup

Allows you to query the Bugtraq and RTI databases.

Bug reports and RTI's are displayed in a popup
window.  When the window is unpinned, it will be
reused for the next query.  When pinned, a new
popup will be created for the next query.
##################################################
:query_list
Query List

A list of Bugtraq and RTI queries.  A double-click
on a list item will initiate the query.
##################################################
:query_db
Database

RTIs		Query the RTI database.

Bugtraq		Query the Bugtraq database.
##################################################
:query_bugid
Bugid/RTI #

The number of the bug or RTI to query.

RTI's are assigned the same number as the bugid
which it addresses.  RTI's with multiple bugids
are assigned the number of the first bug listed
in the original create message.  Patch RTI num-
bers begin with a 'P'.

A return on this field will initiate the query.
##################################################
:query_button
Query

Initiate the query.

Querying a RTI will match all RTIs with that
number; implementor, patch, and archived patches.
The names of the RTI files matched will be
displayed in the scrollable list below.  If only
one match is found, it will automatically be
shown.  If more than one match is found, the RTI
can be displayed by either selecting the file
name and pushing the "Show" button or by
double-clicking on the file name.

Querying a bugid in bugtraq will automatically
display the information from bugtraq.
##################################################
:query_mlist
Query Match List

A list of RTI files matched from a RTI query.
A double-click on a list item will automatically
display the RTI.
##################################################
:query_show
Show

Display the RTI selected in the query match list.
##################################################

##################################################
#
# Implementor Props Window
#
##################################################
:props_irti_general
Implementor Props Sheet

Allows you to set properties related to the
Implementor template.
##################################################
:props_irti_advocate
CRT Advocate

The email address of the CRT advocate who will
evaluate the RTI.  The address must be relative
to a Sun NIS domain (<user>@<domain>).

The special name "Default" (or "default") may
be specified to assign the RTI to the default
advocate who will pick a CRT member to evaluate
the RTI.  This should *only* be used when you
do not know who to assign the RTI to.

An associated popup menu lists of all of the CRT
advocates by their email address and areas of
expertise.
##################################################
:props_irti_target
Target Release

The code name of the ON release you plan to
integrate this change into.
##################################################

##################################################
#
# Feedback Window
#
##################################################
:feedback_general
Feedback Popup

Send bug reports, questions, comments, etc. to
the rtitool development team.
##################################################
:feedback_mailto
Mail To

Address of the rtitool feedback alias.
##################################################
:feedback_subj
Subject

Subject of the mail message.
##################################################
:feedback_mailcc
Mail Cc

Address of where to send a copy of the message.
##################################################
:feedback_send
Send

Sends the mail message to the addresses in the
Mail To: and Mail Cc: text fields.
##################################################
:feedback_reset
Reset

Reset the fields and compose text window.
##################################################

##################################################
#
# Evaluator Props Window
#
##################################################
:props_erti_general
Evaluator Props Sheet

Allows you to set properties related to the
Evaluator template.
##################################################
:props_erti_crtid
Open RTI's for

The name used to build the "Open RTI's for" list.
The value may be either a login name, email name,
or complete email address.

The special name "Default" (or "default") may
be specified to find all RTI's assigned to the
default advocate.

If this field is left blank, a list of all open
RTI's will be displayed.

An associated popup menu lists of all of the CRT
advocates by their email address and areas of
expertise.
##################################################
:props_erti_fwdto
Forward To

The email address of the CRT advocate to forward
your CRT assignments to.  The address must be
relative to a Sun NIS domain (<user>@<domain>).

The special name "Default" (or "default") may
be specified to forward your assignments to the
default advocate.

An associated popup menu lists of all of the CRT
advocates by their email address and areas of
expertise.
##################################################

##################################################
#
# Patch Props Window
#
##################################################
:props_patch_general
Patch Props Sheet

Allows you to set properties related to the
Patch template.

##################################################
#
# Risk & Impact Window
#
##################################################
:risk_general
Risk & Impact

Allows you to specify the Impact, Type of Impact
and Risk of a change to the SunOs and/or Solaris
product.
:risk_impact
##################################################
Impact

Please assess the impact of this change on the 
SunOS and/or Solaris product.

If the impact is non-null, you will need to
specify the Type-of-impact below.
##################################################
:risk_impact_0
NONE

No impact.
##################################################
:risk_impact_1
VERY LOW

Very low impact.
##################################################
:risk_impact_2
LOW

Low impact.
##################################################
:risk_impact_3
MEDIUM

Medium impact.
##################################################
:risk_impact_4
HIGH

High impact.
##################################################
:risk_impact_5
VERY HIGH

Very high impact.
##################################################
:risk_type
Type of impact

Indicate which product areas will be impacted by
this change.  More than one type of impact may
apply.

Additional information and/or details should be
included in the Comments field, if necessary.
##################################################
:risk_type_a
API changes

Please indicate whether this change modifies the
behavior of a function or changes the input or
output of a function.

Please indicate whether this change modifies the
behavior of a command or changes the usage of a
command in any way.	

Details should be provided in the Impact/Interface
Changes section.
##################################################
:risk_type_h
header file changes

Please indicate whether this change includes ANY
semantic change to an exported header file.

Details should be provided in the Impact/Interface
Changes section.
##################################################
:risk_type_p
packaging/namespace changes

Packaging and namespace impact includes changes
to file permissions, ownership, path, name and
containing package.

Details should be provided in the Impact/Impact
on Packages section.
##################################################
:risk_type_d
documentation/man page changes

Doc and man page impact includes any required
change to any document or man page as a result
of this work.

Please coordinate with the tech pubs folks to
make sure these changes happen!  The tech pubs
folks do not receive notice of this RTI.
##################################################
:risk_type_o
other changes

Any impact which does not fall into the above
categories.  Please describe in the Comments
section.
##################################################
:risk_risk
Risk

Please assess the risk of this change to the SunOS
and/or Solaris product.
##################################################
:risk_risk_1
VERY LOW

Obvious impact.
##################################################
:risk_risk_2
LOW

Obvious impact.  Little chance of unexpected side effects.
##################################################
:risk_risk_3
MEDIUM

Change is well understood but significant.  Possible side effects.
##################################################
:risk_risk_4
HIGH

Change is in a critical area.  Probable side effects.
##################################################
:risk_risk_5
VERY HIGH

Change is large.  Change is in a critical area.  Not well understood.
##################################################
:risk_apply
Apply

Apply the impact, type of impact, and risk to
all bugids in the Bugids textsw.

To apply to specific bugid or set of bugids,
select those lines in the Bugids text window and
the select the Apply button.
##################################################
:risk_reset
Reset

Remove all selections.
##################################################

##################################################
#
# Implementor Window
#
##################################################
:irti_general
Implementor Template

Allows you to compose implementor RTI messages to
create, update, and cancel RTI's.
##################################################
:irti_mailto
Mail To

The email address of where to send the RTI
message.  This must be a valid address to the
rtiroute software.
##################################################
:irti_mailcc
Mail Cc

The email address of where to send a copy of the
RTI message.
##################################################
:irti_advocate
CRT Advocate

The email address of the CRT advocate who will
evaluate the RTI.  The address must be relative
to a Sun NIS domain (<user>@<domain>).

The special name "Default" (or "default") may
be specified to assign the RTI to the default
advocate who will pick a CRT member to evaluate
the RTI.  This should *only* be used when you
do not know who to assign the RTI to.
##################################################
:irti_advocate_menu
CRT Advocate Menu

A list of all of the CRT advocates by their email
address and areas of expertise.
##################################################
:irti_action
Action

------->create		

Result:		Creates a new RTI.

Req'd Fields:	Most fields are required, but not
		all.

------->update

Result:		Updates the information on an
		existing RTI.

Req'd Fields:	Only RTI # required.  All other
		fields are optional, but you
		should ONLY fill in the fields
		you want to modify!

Note on
    Bugids:	An update to the bugids field
		replaces the previous value. If
		you need to add to, delete from,
		or change the value of bugids,
		you'll need to include the
		complete information.

------->resubmit

Result:         Reopens an RTI that has already
 	        been accepted or cancelled or is
                in the expired or hold state.
                Used when a stale RTI needs to
                be reconsidered, i.e.  the RTI
                was approved for dev,dev has
                ended and the RTI wasn't        
                integrated during that period.
                Causes the RTI to be reevaluated.  

Req'd Fields:	Only RTI # required.  All other
		fields are optional, but you
		should ONLY fill in the fields
		you want to modify from the
		original create.

Note on
    Bugids:	See update.

------->cancel

Result:		Cancels an RTI.
##################################################
:irti_rtinum
RTI #

The number of a RTI to update or cancel.

RTI's are assigned the same number as the bugid
which it addresses.  RTI's with multiple bugids
are assigned the number of the first bug listed
in the original create message.
##################################################
:irti_reviewer
Code Reviewed By

The email address(es) of the peer(s) who code
reviewed this work.  The addresses must be
relative to a Sun NIS domain (<user>@<domain>).

Note that a code review is required prior to the
creation of any ON integration.

Code review is VERY important in all phases of
development.  To quote Tim Marsland:

   "Code review is our most important weapon
    against introducing brokenness.  This cannot
    be emphasized too strongly."
##################################################
:irti_release
Target Release

The code name of the ON release you plan to
integrate this change into.
##################################################
:irti_flags
Flags

A selection of alerts to the evaluator concerning
this RTI.

PATCHED		This bug fix is included in a CTE
		patch for a previous release.

CLEAR		Clear (reset) the flags in the RTI

For an update or resubmit action, selecting no flags
preserves any previous value in the RTI.  Because
of this, the special flag CLEAR is used to remove
all flags.
##################################################
:irti_bugids
Bugids

Open the Bugids window.
##################################################
:irti_arc
ARC Opinion

Open the ARC Opinions window.
##################################################
:irti_comments
Comments

Open the Comments window.
##################################################

##################################################
#
# Implementor Bugids Window
#
##################################################
:bugids_general
Bugids Popup

Allows you to create bugid(s) one-liner which
contains the bugid, priority, severity, impact,
type-of-impact, risk, and synopsis from bugtraq.
##################################################
:bugids_bugtraq
Bugtraq Lookup

Lookup the bugids listed in the text window in
Bugtraq.

By default, all bugids will be looked up.  To 
look up a specific bugid or set of bugids, select
those lines in the Bugids text window before
selecting this button.
##################################################
:bugids_risk
Risk & Impact

Open the Risk & Impact window.
##################################################
:bugids_reset
Reset

Reset (clear) the Bugids text window.
##################################################

##################################################
#
# Implementor ARC Opinions Window
#
##################################################
:arc_general
ARC Opinions Popup

ARC opinion popup to be used when supplying ARC
opinion or case numbers relevant to the 
implementor RTI which the CRT advocate may wish 
to reference in evaluating the RTI.
##################################################
:arc_list
ARC Opinions List

The list of ARC Opinions or Cases to be inserted
into the RTI mail message.
##################################################
:arc_add
Add

Add the ARC Opinion or Case the list.
##################################################
:arc_delete
Delete

Delete the selected item from the list.
##################################################
:arc_reset
Reset

Reset (clear) the ARC Opinions list.
##################################################
:arc_arc
ARC

A selection of existing ARC committees which might
have written an opinion relevant to the 
implementor RTI.
##################################################
:arc_year
Year

Year in which the ARC opinion or case would have
been filed.  This is relevant since ARC opinions
are indexed by:
	ARC name/Year/Opinion number
##################################################
:arc_opinion
Opinion Number

Opinion or case number assigned by the ARCs to 
the case in question.
##################################################

##################################################
#
# Comments Window
#
##################################################
:comments_general
Comments Popup

Allows you to attach comments to your RTI mail
message.
##################################################
:comments_reset
Reset

Reset (clear) the comments text window.
##################################################

##################################################
#
# Evaluator Window
#
##################################################
:erti_general
Evaluator Template

Allows you to compose evaluator RTI messages to
accept, hold, and reassign RTI's.  You can also
forward you RTI assignments to another advocate.
##################################################
:erti_mailto
Mail To

The email address of where to send the RTI
message.  This must be a valid address to the
rtiroute software.
##################################################
:erti_mailcc
Mail Cc

The email address of where to send a copy of the
RTI message.
##################################################
:erti_crtid
Open RTI's for:

The name used to build the "Open RTI's for" list.
The value may be either a login name, email name,
or complete email address.

The special name "Default" (or "default") may
be specified to find all RTI's assigned to the
default advocate.

If this field is left blank, a list of all open
RTI's will be displayed.
##################################################
:erti_crtid_menu
Open RTI's for: Menu

A list of all of the CRT advocates by their email
address and areas of expertise.
##################################################
:erti_forward
Forward

Open the Forward popup.
##################################################
:erti_rtilist
Open RTI List

The list of open RTI's for the advocate specified
in the "Open RTI's for:" text field.  A open RTI
is defined as a RTI in the open, hold, or expired
state.

Patch RTI numbers are preceded by a 'P' and appear
first in the list.
##################################################
:erti_update
Update List

Rebuild the Open RTI's list.
##################################################
:erti_rtinum
Replying to RTI #

The number of the RTI to accept, hold, or
reassign.

RTI's are assigned the same number as the bugid
which it addresses.  RTI's with multiple bugids
are assigned the number of the first bug listed
in the original create message.

Patch RTI numbers are preceded by a 'P'.
##################################################
:erti_action
Reply

accept		Accept a RTI.

hold		Place a RTI on hold.

reassign	Reassign a RTI to another CRT
		advocate.

cancel		Cancel a RTI.
##################################################
:erti_comments
Comments

Open the comments popup.
##################################################
:erti_reassign
Reassign To:

The email address of the CRT advocate to reassign
a RTI to.  The address must be relative to a Sun
NIS domain (<user>@<domain>).

The special name "Default" (or "default") may
be specified to reassign to the default advocate.
##################################################
:erti_reassign_menu
Reassign To Menu

A list of all of the CRT advocates by their email
address and areas of expertise.
##################################################
:erti_release
Integrate Into

A list of the various releases the change may be
integrated into.  If approving an RTI to integrate,
the CRT advocate needs to specify into which release
the submitter should integrate the fix.  
##################################################

##################################################
#
# Forward Window
#
##################################################
:fwd_general
Forward

The Forward popup allows you to forward your own
or a another advocate's CRT assignments. An
advocate's assignments should be forwarded when-
ever they will be unavailable to evaluate RTI's.

You can only remove a forward for yourself.  A
forward should be removed as soon as the you
are available again for RTI evaluations.

A message will automatically be sent to the
forwardee each time a forward is installed or
removed.

If a forward is installed for an advocate by
someone else, a message will be sent to that
advocate to inform them that their assignments
are being forwarded.

If a forward loop is detected or if the forward
destination is not a CRT advocate, the assign-
ments will be forward to the default advocate
You will receive an error email message informing
you when this happen.  Please correct these
situations by selecting another person to forward
to as soon as possible.
##################################################
:fwd_send
Send

Send a forward/unforward message to the address
defined my "Mail To:" in the evaluator windows.
If "Mail Cc:" is defined, a copy will be sent to
this address.

##################################################
:fwd_reset
Reset

Reset the Forward popup fields.
##################################################
:fwd_state_button
Current State Button

Updates the current forwarding state for the
advocate listed in the "Forward From:" text
field.  If this field is blank, the state for
the current user is displayed.
##################################################
:fwd_state
Current State

Shows the current forwarding state for the
advocate listed in the "Forward From:" field or
the current user if that field is blank.

If the advocate's assignments are currently
forwarded, the state will be "Forward to
<advocate>".

A state of "Unable to determine" indicates either:

  1)  There is no forwards.db defined in the
      system rtitool.config file.

  2)  An open of the forwards.db failed.

  3)  The advocate is not in the CRT advocate
      list.

##################################################
:fwd_action
Action

Provides these choices:

forward 	Forward CRT assignments to the
		advocate listed in the "Forward
		To:" text field.

unforward	Remove any forwarding for the
		current user.  Your CRT assign-
		ments will now be sent to you.
##################################################
:fwd_fwdfrom
Forward From

Specifies the advocate to forward CRT assignments
for.  If this field is blank, assignments for the
current user will be forwarded.

A valid email address relative to a Sun domain
(<user>@<domain>) must be given.  A list of the
CRT members is available via the associated popup
menu.
##################################################
:fwd_fwdfrommenu
Forward From Menu

Gives a list of the CRT members.  Selecting an
item from this menu will fill in the "Forward
From" text field with the advocate's email
address.
##################################################
:fwd_fwdto
Forward To

Specifies the advocate to forward CRT assignments
to.

A valid email address relative to a Sun domain
(<user>@<domain>) must be given.  A list of the
CRT members and their areas of expertise is
available via the associated popup menu.
##################################################
:fwd_fwdtomenu
Forward To Menu

Gives a list of the CRT members and their areas
of expertise.  Selecting an item from this menu
will fill in the "Forward To" text field with
the advocate's email address.
##################################################
:fwd_current_fwds
Current Forwards

A list of the currently installed forwards. 
##################################################
:fwd_update
Update List

Re-read the list of current forwards.
##################################################

##################################################
#
# Patch Window
#
##################################################
:patch_general
Patch Template

Allows you to compose patch RTI messages.
##################################################
:patch_mailto
Mail To

The email address of where to send the patch RTI
message.  This must be a valid address to the
prtiroute software.
##################################################
:patch_mailcc
Mail Cc

The email address of where to send a copy of the
patch RTI message.
##################################################
:patch_action
Action

------->create		

Result:		Creates a new RTI.

Req'd Fields:	Most fields are required, but not
		all.

------->update

Result:		Updates the information on an
		existing RTI.

Req'd Fields:	Only RTI # required.  All other
		fields are optional, but you
		should ONLY fill in the fields
		you want to modify!

Append vs.
    Replace:	Keyword/value fields such as
		'Code Reviewed By:' replace the
		previous value.  Multi-line
		fields such as 'Description:'
		append the updated text to the
		existing text.  Exceptions to
		this are:

		    Bugids
		    Deliverable Source Files
		    Deliverable Objects/Binaries
                    Releases to Patch

		which REPLACE the previous value.
		If you update any of these fields,
		you'll have to include any pre-
		vious information you wish to
		retain.

Update vs.
     Resubmit:  If a patch RTI has already been 
		accepted, you should take care
		what action you use to update
		field values.  Significant changes
		must be modified with a "resubmit"
		action, rather than an "update", 
		since such changes will require
		re-approval by the CRT advocate.  
		
		The fields whose modification 
		would cause significant changes, 
		requiring a "resubmit" are:

			Bugids
			Releases
			Deliverables
			Impact
			Point Patch
		
		If the patch RTI has not yet been
		accepted, or fields other than
		those listed above are modified,
		an "update" will suffice.  

------->resubmit

Result:         Reopens an RTI that has already
 	        been accepted or cancelled or is
                in the expired or hold state.
                Used when a stale RTI needs to
                be reconsidered; causes the RTI
                to be reevaluated.  

Req'd Fields:	Only RTI # required.  All other
		fields are optional, but you
		should ONLY fill in the fields
		you want to modify from the
		original create.

Append vs.      
    Replace:    See update.

Update vs.
    Resubmit:	See update.

------->cancel

Result:		Cancels an RTI.
##################################################
:patch_rtinum
RTI #

The number of a Patch RTI to update or cancel.

All Patch RTI numbers begin with a 'P'.

RTI's are assigned the same number as the bugid
which it addresses.  RTI's with multiple bugids
are assigned the number of the first bug listed
in the original create message.
##################################################
:patch_id
Patch ID

This value may not be available.  This is not a
required field.

If you requested a patchid in advance or the
patchid has been given to a customer in advance,
please specify the patchid here.
##################################################
:patch_esc
CTE Escalation #

The Escalation number from bugtool's Escalation
popup for the bugid(s) associated with this patch.
##################################################
:patch_requestor
Patch Requestor

Email address of CTE or Sun contact who requested
the patch.  The address must be relative to a Sun
NIS domain (<user>@<domain>).

The patch gatekeeper will deliver the patch to
this person for customer verification.
##################################################
:patch_security
Security Bug

We are required to flag security problems in the
README that accompanies the patch.  Please
indicate if this is a security bug.
##################################################
:patch_reviewer
Code Reviewed By

The email address(es) of the peer(s) who code
reviewed this work.  The addresses must be
relative to a Sun NIS domain (<user>@<domain>).

Note that a code review is required prior to the
creation of any ON patch.

Code review is VERY important in all phases of
development.  To quote Tim Marsland:

   "Code review is our most important weapon
    against introducing brokenness.  This cannot
    be emphasized too strongly."
##################################################
:patch_irelease
Commit to Integrate In:

Select the release you plan to integrate this fix
into.  If this fix is not planned to be included
in a future release, select N/A.

Remember, it is your responsibility to ensure that
a patch is fixed in the NEXT release!

If it is not fixed in the next release, you will
need to create a patch for the next release. 
##################################################
:patch_releases_general
Patch Releases

Specify which releases need to be patched.

For releases which support multiple architectures,
specify which architectures should have patches
generated.

The codename to release name mapping is:

	callisto	5.0
	phobos		5.1
	on493		5.2
	on1093		5.3
	on494		5.4
	on495		5.5
	on596		5.5.1
##################################################
:patch_releases_reset
Reset

Reset the Patch Releases popup.
##################################################
:patch_usual_answer
Usual Answer(s)

A choice of the typical answer(s) for this field.
Selecting a usual answer disables the Textsw.
##################################################
:patch_desc_general
Problem Description

Describe the problem the patch addresses.
##################################################
:patch_desc_reset
Reset

Reset (clear) the Problem Description text window.
##################################################
:patch_deliver_src
Deliverable Source Files:

List of file updates, deletes, creates, renames.
You can obtain this list using putback -n in
the patch workspace.
##################################################
:patch_deliver_srcreset
Reset

Reset (clear) the Deliverable Source Files text
window.
##################################################
:patch_deliver_obj
Deliverable Objects/Binaries

List objects needing redelivery to customer as a
result of this patch.
##################################################
:patch_deliver_objreset
Reset

Reset (clear) the Deliverable Objects/Binaries
text window.
##################################################
:patch_impact_pkg
Impact on Packages

List all changes that will impact the creation of
install packages.  Imagine what is changing from
the customer perspective--the items being install-
ed and their attributes.  We need to know about
changes in installed directories, files, and hard
and soft links.  Changes include permissions,
owner, group, and location; so, reorganizations,
renames, creations, and deletions are important.

The answer here will usually be NONE, since this
is a patch.
##################################################
:patch_impact_pkgreset
Reset

Reset (clear) the Impact on Packages text window.
##################################################
:patch_impact_ui
Interface Changes

Are you changing any interfaces?  Changes to a
header file which we ship on the CD are by
definition changes to interfaces.

Highlight any interface changes and explain why
they are necessary.

The answer here will usually be NONE, since this
is a patch.
##################################################
:patch_impact_uireset
Reset

Reset (clear) the Interface Changes text window.
##################################################
:patch_impact_in
Impact on Installation

Is any special action required of the customer at
the time of installation?

Do any postinstall/preinstall scripts need to be
written to accommodate for the special install-
ation requirements of this patch?

Note that standard installation instructions for
all patches include the recommendation to reboot
after patch installation.
##################################################
:patch_impact_inreset
Reset

Reset (clear) the Impact on Installation text
window.
##################################################
:patch_origin_patch
Patch Request Origin

Specify the origin of the patch request/
escalation.  This is a required field which 
does a replace on update.

A patch is either generated due to an external
request (CTE escalation) or internal request.  
Within these two categories, select one of the 
following choices from the pulldown menu:

- FCS bug:
  bug occurs in the FCS version of the OS; it is 
  not caused by another patch
- Patch regression:
  bug is caused by the presence of another patch
- New feature:
  patch is an RFE (request for enhancement)
##################################################
:patch_origin_addl_info
Patch Request Origin--Additional Info

Provide any elaboration on the above Patch Request
Origin choice here.  Unlike the Patch Request 
Origin field, this field will append updated
text to the existing text.
##################################################
:patch_origin_reset
Reset

Reset (clear) the Patch Request Origin field 
and Patch Request Origin--Additional Info window.
##################################################
:patch_just_patch
Patch Justification

Categorize the type of problem that justifies
this patch.

Provide an explanation of why the patch is needed
and why you and the Responsible Manager decided
to create the patch.
##################################################
:patch_just_choices
Patch Justification Choices

A list of common reasons to justify a patch.
Multiple choices are allowed.

An explanation of why the patch is needed should
be included via the text window.
##################################################
:patch_just_reset
Reset

Reset (clear) the Patch Justification text window.
##################################################
:patch_just_point
Point Patch Justification

A patch should be a point patch if you think it so
risky and/or problematic that it should NOT be
automatically included in the next patch to the
same deliverable object.

To accomplish this, point patches are NOT
integrated into the cumulative patch source base.

As a result, point patches are NOT guaranteed to
interoperate with other patches; point patches
will definitely not interoperate with other
patches to the same deliverable object.

Point Patches are rare and expensive.  They are
only justified in extraordinary circumstances.
##################################################
:patch_just_pointreset
Reset

Reset (clear) the Point Patch Justification text
window.
##################################################
:patch_test_general
Test Results:

Specify objects, patches tested.

List any unit testing done, test suites run
and/or any other testing.

List hardware on which deliverables were tested.
##################################################
:patch_test_reset
Reset

Reset (clear) the Test Results text window.
##################################################
:patch_releases
Releases

Open the releases popup.
##################################################
:patch_bugid
Bugids

Open the bugids popup.
##################################################
:patch_arc
ARC Opinion

Open the ARC Opinions window.
##################################################
:patch_desc
Description

Open the description popup.
##################################################
:patch_deliver
Deliverables

Open the deliverables popup.
##################################################
:patch_impact
Impact

Open the impact popup.
##################################################
:patch_just
Origin/Justification

Open the patch request origin and 
justification popup.
##################################################
:patch_pointjust
Point Patch

Open the point patch popup.
##################################################
:patch_test_results
Test Results

Open the test results popup.
##################################################
:patch_comments
Comments

Open the comments popup.
##################################################
