#
#ident  "%Z%%M%   %I%   %E% SMI"
#
# Copyright (c) 1998 by Sun Microsystems, Inc.
#

#
# NOTE:  Sites which do not have the /shared/ON automount map will need
# to replace /shared/ON with /net/wizard.Eng/export/consolidation/rtiroute.
#

#
#	Bugtraq+ defaults
#
#rtitool.bugtraq.username:       THRUO
#rtitool.bugtraq.password:       dOITO^~UHN
rtitool.bugtraq.username:      IOROTTW
rtitool.bugtraq.password:       dH^K^PXZI
rtitool.bugtraq.sybase:         /usr/dist/share/sybase/5.x

#
#	Implementor defaults
#
rtitool.implementor.mailto:		on-crt@lizard.Eng
rtitool.implementor.targetrelease:	""
rtitool.implementor.releases:		on81
#rtitool.implementor.flags:		PATCHED

rtitool.arc.opinionnumber:		XXX
rtitool.arc.approvaldate:		MM/DD/YY
rtitool.implementor.cmtsdesc:	\
List any additional information and justification.

#
#	Evaluator defaults
#
rtitool.evaluator.mailto:		on-crt@lizard.Eng
rtitool.evaluator.rtidatabases:		\
/shared/ON/rtiroute_db/newrtis,\
/shared/ON/rtiroute_db/oldrtis,\
/shared/ON/rtiroute_db/newprtis,\
/shared/ON/rtiroute_db/oldprtis,\
/shared/ON/rtiroute_db/patch-archives,\
/shared/ON/rtiroute_db/archives/493rtis,\
/shared/ON/rtiroute_db/archives/1093rtis,\
/shared/ON/rtiroute_db/archives/494rtis,\
/shared/ON/rtiroute_db/archives/495rtis,\
/shared/ON/rtiroute_db/archives/596rtis,\
/shared/ON/rtiroute_db/archives/297rtis,\
/shared/ON/rtiroute_db/archives/998rtis
rtitool.evaluator.releases:		on81
rtitool.evaluator.cmtsdesc:	\
Please explain or comment on your action.

#
#	Patch defaults
#
rtitool.patch.mailto:			on-crt@lizard.Eng
rtitool.patch.integratereleases:	on81,N/A
rtitool.patch.justchoices:		\
High call generator,\
Data corruption,\
System panics frequently,\
Security,\
Serious regression introduced in previous patch,\
Other
rtitool.patch.releases:			\
5.0: sparc,\
5.1: sparc,\
5.2: sparc,\
5.3: sparc,\
5.4: sparc i386,\
5.5: sparc i386,\
5.5.1: sparc i386,\
5.6: sparc i386,\
5.7: sparc i386,\
5.8: sparc i386

#
# Patch Descriptions
#
# NOTE:  Lines are separated by a ','.  To but a comma in the description,
#        it needs to be escaped.
#
rtitool.patch.relsdesc:			\
When selecting which releases to patch\, select the,\
release the bug was escalated against\, and also keep,\
in mind the patch forward porting policy.,,\
Do not submit a separate RTI for each release to,\
patch; you can specify multiple releases per one,\
patch RTI.,,\
Select all architectures for which a patch should be,\
generated.  For common code changes\, you should,\
select all architectures.,,\
Specify all appropriate releases and architectures now.

rtitool.patch.probdesc:			\
Problem description:,,\
Describe the problem the patch addresses.

rtitool.patch.srcdesc:			\
Deliverable Source Files:,,\
List all file updates\, deletes\, creates\, and renames.,\
Indicate if any of the deliverable source file(s) differ among the,\
targeted releases to patch.,\
Use full pathnames to source file from $SRC\, e.g.\, usr/src/cmd/ls/ls.c.

rtitool.patch.objdesc:			\
Deliverable Objects/Binaries:,,\
List all objects/binaries needing redelivery to the customer as a result,\
of this particular change.  If your change entails headers\, libraries\,,\
or binary interfaces\, take particular care to tell us what needs to ship.,,\
If you have listed a header file under 'Deliverable Sources' and,\
you have changed a public documented interface\, make sure you list,\
the header file as a 'Deliverable Object/Binary'.,,\
Do not unnecessarily group objects together that have no interdependencies.,\
Doing so will result in having unrelated objects in the same patch.,,\
Indicate if any objects/binaries need to be deleted from the installed system.,,\
Indicate if any of the deliverable object file(s) differ among the,\
targeted releases to patch.,,\
List installed location for the object file relative to $ROOT\, e.g. usr/bin/ls.,,\

rtitool.patch.impactdesc:		\
Impact on Packages:,\
List all changes that will impact the creation of install packages. Include changes to,\
all directories\, files\, and hard and soft links. Changes include additions\, deletions\,,\
and modifications to permissions\, owner\, group and location.

rtitool.patch.ifacedesc:		\
,\Interface Changes:,\
List any and all interface changes involved in this patch\, including public\, sun,\
private\, consolidation private\, project private and internal interfaces.,\
It is UNACCEPTABLE to break another product or application in a patch.,\
Explain the rationale in deciding that the proposed interface change is benign.,\
List who you discussed this with.

rtitool.patch.installdesc:		\
,\Impact on Installation:,\
List any special actions required of the customer at the time of installation.,\
List any pkg installation scripts (such as postinstall or preinstall) which need to,\
accompany your patch.  Provide a pointer to the script you have created or attach it here.,\
If you are providing a i.<class> (class action script) to edit a file\,,\
please provide a r.<class> (remove class action script) or u.<class> script,\
that will undo the changes introduced by the i.<class> script.

rtitool.patch.origindesc:		\
Specify the origin of the patch request/escalation from the pulldown menu below.,,

rtitool.patch.originaddldesc:		\
,Provide additional explanation\, if needed.,,\
Patch Request Origin--Additional Info:

rtitool.patch.justdesc:			\
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.

rtitool.patch.ptjustdesc:		\
Point Patch Justification:,,\
Point Patches are rare and expensive.  They are only justified in extraordinary,\
circumstances.,,\
If and only if you propose that this be a point patch\, provide the justification,\
here.

rtitool.patch.testdesc:			\
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.

rtitool.patch.cmtsdesc:			\
List any additional information and justification.,,\
Indicate any patch incompatibilities and patch requirements,\
as a result of your bugfix(es).

#
#	Message at bottom of each template panel
#
rtitool.templates.mesg:			\
Press your Help key for context-sensitive spot help.

#
#	Properties.General
#
rtitool.props.general.startingtemplate:		Implementor
rtitool.props.general.dsquery:			BUGTRAQ
rtitool.props.general.rtilogchoice:		No
rtitool.props.general.rtilogdirectory:		$HOME/RTI
rtitool.props.general.rtilogfile:		rtilog

#
#	Risk & Impact
#
# Note #1: If a set a strings contain "||", the text following it wil be
# lined up in the window.
#
# Note #2: These codes/explainations are also in rtitool.general_help and
# rtitool.info.  If you change anything here, be sure those files also
# reflect the changes.
#
rtitool.bugid.impact.choices:	\
0 = NONE,\
1 = VERY LOW,\
2 = LOW,\
3 = MEDIUM,\
4 = HIGH,\
5 = VERY HIGH

rtitool.bugid.type.choices:	\
a = API changes,\
h = header file changes,\
p = packaging/namespace changes,\
d = documentation/man page changes,\
o = other changes

rtitool.bugid.risk.choices:	\
1 = VERY LOW. ||Obvious impact.,\
2 = LOW. ||Obvious impact.  Little chance of unexpected side effects.,\
3 = MEDIUM. ||Change is well understood but significant.  Possible side effects.,\
4 = HIGH. ||Change is in a critical area.  Probable side effects.,\
5 = VERY HIGH. ||Change is large.  Change is in a critical area.  Not well understood.

#
#	Misc.
#
rtitool.sendfeedbackto:			rtitool-comments@lizard.Eng
rtitool.advocates.config:		advocates.config
rtitool.forwards.db:			/shared/ON/rtiroute_db/forwards.db
rtitool.arcs:				PSARC,ASARC,LSARC,HPARC,FWARC,SPARC

#
# added by rhogue 970804
#
rtitool.default.advocate.email:     "crt-def-advocate"
rtitool.default.advocate.logname:   "crt-def-advocate"
rtitool.default.advocate.domain:    "lizard"
rtitool.default.advocate.expertise: "default advocate"
