Hi Miyuru, I think we should not do this. This complicates the current model. The whole point of defining this patch model is,
- we only provide patches/bug fixes - no api changes - ideally the fixes should not break the current stuff. If so, why can't we apply your fixes to patch0001 ? If you get it correct then the ESB release will go with patch0001, if you don't then tough luck, you have to fix more bugs with patch0002. For an example if we had this fixes in the released Carbon kernel, then there is no need to have patch releases at all. There is no relationship between patch releases and individual product releases. when we have two parallel patch versions, the need of double commit arises. which is not correct. I think we should remove patch0002 till patch0001 kernel get released. thanks, --Pradeep On Tue, Apr 23, 2013 at 3:08 PM, Miyuru Wanninayaka <[email protected]> wrote: > This patch has changes need for ESB 4.7 release. > > Patch0001 will release with 3rd of March release and ESB 4.7 will go > later. So we are keeping ESB 4.7 related patches in patch0002 > > > On Tue, Apr 23, 2013 at 12:30 PM, Kishanthan Thangarajah < > [email protected]> wrote: > >> Hi All, >> Any specific reason for this? Since patch0001 is not yet released, we can >> still add those components in patch0002 [1] to 0001. >> >> Thanks, >> Kishanthan. >> [1] >> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.1.0/patches/patch0002/ >> -- >> *Kishanthan Thangarajah* >> Software Engineer, >> Development Technologies Team, >> WSO2, Inc. >> lean.enterprise.middleware >> >> Mobile - +94773426635 >> Blog - *http://kishanthan.wordpress.com* >> Twitter - *http://twitter.com/kishanthan* >> > > > > -- > Miyuru Wanninayaka > Senior Software Engineer - WSO2 Inc > +94-772099788 > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Pradeep Fernando* Member, Management Committee - Platform & Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
