IST Site Navigation:
The Release Management and Quality Assurance Testing Unit serves as the gate-keeper to the campus production environment. (QA testing is currently performed at the application developer/functional user level while we continue to build a testing team. The QA unit requires proof of testing prior to migrating from test to production.)
This unit is responsible for ensuring successful application releases (i.e., introduction of hardware and software changes into the operating environment) with minimum disruption to the operating environment.
RM/QA administers controls to prevent risks or failure to the campus operations and to ensure that any new development or changes to existing applications do not jeopardize the integrity of the campus systems.
Services: Quality assurance and performance testing; migration of software to qa and production; repository (cvs and svn) administration services; JIRA system administration services.
Primary contact:
Release Management Team:
General question regarding Release Management and Quality Assurance Testing should be submitted to:
Migrations (Unix):
The primary means of requesting migrations from the Release Management team is through the JIRA project management system (code management, bug tracking, etc) Application Services Migration Project (AS Migrations “SISM”).
Release Management general requirements [Word]
JIRA Developer Migration Request Guidance [Word]
Migrations (Mainframe):
The primary means of requesting migrations on the Mainframe is through the Alchemist system. Projects not yet moved into the Alchemist system migration requests are handled through the Footprints system.
Requests for migrations go through:
https://footprints.berkeley.edu/ under the “IST AS Release Management” project.
Migrations (Windows):
The primary means of requesting migrations for the Windows systems is through the Footprint system.
Requests for migrations go through:
https://footprints.berkeley.edu/ under the “IST AS Release Management” project.
JIRA Project
(https://beartracks.berkeley.edu/jira/secure/Dashboard.jspa ):
The Release Management team also administers the JIRA project management system. Requests for support to the JIRA administrator should be sent to:
Duties include:
The standard set up for JIRA projects information can be found at:
http://ist-dev.berkeley.edu/as/ag/tools/usage/jira-standards-ist.html
Information on Project Permissions and Issue Level Security:
http://ist-dev.berkeley.edu/as/ag/tools/usage/jira-standards-ist.html#Project+Permissions+and+Issue-Level+Security
Information on requesting new projects in JIRA:
http://ist-dev.berkeley.edu/as/ag/tools/usage/jira-standards-ist.html#Creating+new+JIRA+projects
Information on requesting new Jira users accounts:
http://ist-dev.berkeley.edu/as/ag/tools/usage/jira-standards-ist.html#Adding+new+JIRA+users
Subversion Repository:
The Release Management team provides administrative support for the Subversion (svn) code repository. Requests for administrative support for the svn system should be sent to:
Duties include:
Required Information for SVN Support [Word]
Forms:
JIRA New Project Request [Word]
Subversion (SVN) Access Request [Word]
New Projects Requesting Initial Migrations [Word]
SAMS Migration Request [Word]