IST Site Navigation:
The Release Management and Quality Assurance Testing Unit serves as the gate-keeper to the campus production environment.
The unit is responsible for ensuring successful application releases (i.e., introduction of hardware and software changes into the operating environment) and quality testing with minimum disruption to the operating environment.
The QA team currently performs unit testing of applications using the Selenium IDE in the QA environment.
Developers who wish to begin implementation of the Selenium IDE into their migration requests should contact release management (see primary contact information below).
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 (v06)[Word]
Migrations (Mainframe):
Release management responsibilities encompass the following:
Administer standards set for migrations to QA and Production environments when requested by project managers of IST Applications. During the migration process the RM Team member shall work with the application developer and other analysts in resolving problems that come up during migrations. After all avenues are exhausted between the RM Team member and the developer the issue shall be escalated to the next higher level, i.e., Lead Developer, DB2's (DB2 Doctor should be the last resort), etc. to resolve the problem.
When developers require a change to a member within a dataset to support the development process they should create a migration ticket in footprints to the release management team. The release management team member will “rename” the member and wait for a response from the developer as to when it is safe to “delete” the member. All other development issues outside the migration process should be resolved by the developers as stated in the previous paragraph.
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.berkeley.edu/as/ag/tools/usage/jira-standards-ist.html
Information on Project Permissions and Issue Level Security:
http://ist.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.berkeley.edu/as/ag/tools/usage/jira-standards-ist.html#Creating+new+JIRA+projects
Information on requesting new Jira users accounts:
http://ist.berkeley.edu/as/ag/tools/usage/jira-standards-ist.html#Adding+new+JIRA+users
Creating and Working with Jira Issues [PDF]
Project Work Flow [PDF]
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]
New SVN repo-admin Information [Word]
Forms:
JIRA New Project Request [Word]