Bug 777914 (SOA-442) - Update the release process to make sure release manager is defined for each release cycle
Summary: Update the release process to make sure release manager is defined for each r...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-442
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Release Process
Version: 4.2 GA
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.2 CP01
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-26 13:55 UTC by Mark Little
Modified: 2008-04-16 11:03 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-16 11:03:05 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-442 0 None None None Never

Description Mark Little 2008-02-26 13:55:23 UTC
Date of First Response: 2008-03-17 07:42:27
project_key: SOA

At times it seemed that we didn't have an official hand-over of release manager when time zones came into play. Sometimes the left-hand didn't seem to know what the right-hand was doing (or assumed things would happen when they hadn't). At times this wasn't a problem, but at others it lost us precious QE time. So we need an official process where everyone knows who can do the release at a particular time and that individual has full responsibility until/unless passed back to someone else in the team.

Comment 1 trev 2008-03-17 11:42:27 UTC
updated for SOA, waiting for definition for QE person responsible for accepting release


Note You need to log in before you can comment on or make changes to this bug.