Hide Forgot
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"
SOA seems to be the name of choice now so branches should be of the form BossMessaging_1_3_1_SOA_4_2_CP01
OK, please let the various project leads know in time for the SOA Platform release.
Please check this is the case now and close ths issue asap.
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