Bug 777905 (SOA-433)

Summary: Improve release process
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Mark Little <mark.little>
Component: Release ProcessAssignee: Julian Coleman <jcoleman>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: CONTINUING   
Target Milestone: ---   
Target Release: 4.3 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-433
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-08-16 20:48:49 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mark Little 2008-02-21 20:43:26 UTC 
Date of First Response: 2008-02-22 09:13:26
project_key: SOA

We need a release process that does not require a complete re-spin when retagging the last CR to a GA.
Comment 2 Julian Coleman 2008-03-06 15:52:42 UTC 
The summaries from an e-mail exchange are:

> For this option we need to change the internal version strings in the
> run.jar etc. to GA for any potential releases and rely on the build stamp
> (date and time) to identify them once they are unzipped.

> Version.txt is already there so all we have to do is raise a jira for the
> AS, because they are the guys who embed it in the run.jar, I expect JON
> might explode too :-)

> Raise it and discuss it. You've got to remember that none of the projects
> have ever really gone through amount of rigorous QE before, so issues like
> this one probably haven't caused problems in the past (changing the string
> and respinning a release that was not re-QA-ed was the norm).
Comment 3 trev 2008-03-18 14:35:45 UTC 
Link: Added: This issue is related to SOA-451
Comment 5 Mark Little 2008-08-16 20:48:49 UTC 
This is done enough to close. We can open specific issues later if necessary.