Bug 777905 (SOA-433) - Improve release process
Summary: Improve release process
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-433
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Release Process
Version: CONTINUING
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 GA
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-21 20:43 UTC by Mark Little
Modified: 2008-08-16 20:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-16 20:48:49 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777922 0 urgent CLOSED Release check list 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-433 0 None None None Never

Internal Links: 777922

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.


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