Hi All, According to current platform branching strategy, component life-cycle is tightly coupled to platform release cycles. We thought of re-visiting the platform branching strategy.
*requirements*: (there can be more..) - Component life-cycle should be independent from platform release cycles - There should be a mapping between released component and its' corresponding platform release/product release *proposed solution*: - keeping the patch release mechanism as it is. - components can have their own life-cycle. New component starts with 1.0.0 - We capture the mapping information within the qualifier section of the bundle naming. Eg: version scheme of a typical eclipse shipped bundle : major.minor.micro.<qualifier> org.eclipse.equinox.common_3.6.100.v20120522-1841.jar they have included released dates in the qualifier section. Likewise, we can capture the kernel and platform version in the qualifier section. eg: org.wso2.carbon.foo_1.0.0.v420-421.jar 420 - kernel version (with kernel patching strategy, this is not going to change for a given branch) 421 - platform patch release version. Just an example. WDYT ? Thanks, --Pradeep p.s - this mail is a result of an IM conversation (me & Azeez)
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
