Bug 777491 (SOA-3)

Summary:	Make sure all of the projects follow the branching rules
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Mark Little <mark.little>
Component:	Release Process	Assignee:	trev <tkirby>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	unspecified
Target Milestone:	---
Target Release:	4.2 CR3
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-3
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-11-12 15:45:16 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 2007-08-21 11:21:34 UTC

Date of First Response: 2007-08-22 10:44:01
project_key: SOA

Alex Pinkin said:

"We don't have a document but branching strategy was discussed on the app platform calls, and here is how we have agreed to do it.

For each of the ESIP(SOA) platform components a platform branch (a.k.a. stable branch) will need to be created as soon as appropriate component version is tagged. i.e.

For instance, for Messaging 1.3.1 we would create a Branch_1_3_1_ESIP_4_2 off tag:JBossMessaging_1_3_1.

So all of the messaging bug fixes would be done in Branch_1_3_1_ESIP_4_2. Important fixes would need to be back-ported to this branch.

Since we will also be doing cumulative patches for the ESIP (SOA) platform, such branches will be used for all bug fixes that go into the CP's. We would tag stable branches monthly to build cumulative patchs for the platform. i.e. for Messaging

JBossMessaging_1_3_1_ESIP_4_2_CP01 - one month after the ESIP 4.2 release
JBossMessaging_1_3_1_ESIP_4_2_CP02 - two months after the ESIP 4.2 release"

Comment 1 trev 2007-08-22 14:44:01 UTC

SOA seems to be the name of choice now so branches should be of the form BossMessaging_1_3_1_SOA_4_2_CP01

Comment 2 Mark Little 2007-09-02 14:20:37 UTC

OK, please let the various project leads know in time for the SOA Platform release.

Comment 3 Mark Little 2007-11-11 11:26:55 UTC

Please check this is the case now and close ths issue asap.

Comment 4 trev 2007-11-12 15:45:16 UTC

WS JBM and TS are common with EAP and therefore don't need seperate branch
others complying
branches and locations will be documented on red hat web under SOA paltform