Hide Forgot
Date of First Response: 2007-12-06 17:59:06 project_key: SOA SOA Platform Tests - Need a Support/Patch Plan
My thoughts from an email: SOA-P is based on EAP-4.3, but beside patches available for this EAP version, we will have patches strictly related to the SOA-P - for "subcomponents" like esb, smooks, drools, ... which are not present in EAP. Are we going to double the bits available for download? If no subcomponents are involved for a particular CP then we will have one CP for EAP-4.3 and the same CP available for SOA-P. Or do we want to have all CPs for EAP-4.3 also available for SOA-P and additionally another CP for SOA-P "subcomponents"? I don't think that would make sense. Maybe another approach: Create CPs only for SOA-P which would be also applicable for EAP-4.3. Even if the CP would contain patches for esb, drools, etc, it wouldn't affect the EAP-4.3 because these bits aren't there and would be ignored. The version string for SOA-P is currently the same as in EAP 4.3.
The integration of patching models between EAP & SOA-P has yet to be fully addressed. The high-level requirements are here: http://intranet.corp.redhat.com/ic/intranet/JBossEnterpriseServiceIntegrationPlatformPRD.html#Update-Patch However, what we need a is a design document which describes how the SOA-P cumulative patches will be built & delivered in relation to the existing EAP patches. Jaroslaw, can you start a thread on the SOA-engineering list which provides a link to the existing EAP design documents (from CVS?) as a background and which brings up the issues you describe above?
Mark mentioned in an email that the design and implementation of this patch process is the responsibility of the productization team.
Working through this with the productization team.
In discussions with Francois.
We now have a plan for CP and FP. Passing over to Julian to work on the actual plan doc though.
Link: Added: This issue related SOA-236
Let's open specific issues that arise related to this. It's done enough to close this one now.