Hi All, Since now that we have the kernel dev repository available [1], and the current development trunk will be this repository.
During creating the git repository Eranda has merged changes up to patch0005 along with the process. So please merge all the fixes relevant to patch0006 and any other fixes relevant to kernel can be pushed there. Here is the currently applied patch list. The contributor relevant to the below fixes need to push there changes to the dev repo ASAP. https://wso2.org/jira/browse/IDENTITY-2019 - Aselahttps://wso2.org/jira/browse/CARBON-14651 - ManjulaRhttps://wso2.org/jira/browse/CARBON-14654 - AmilaDhttps://wso2.org/jira/browse/ESBJAVA-2051 - Ashansahttps://wso2.org/jira/browse/CARBON-14677 - KasunGhttps://wso2.org/jira/browse/CARBON-14565 - Chanikahttps://wso2.org/jira/browse/ESBJAVA-3010 - GayanChttps://wso2.org/jira/browse/ESBJAVA-1614 - Dinushahttps://wso2.org/jira/browse/IDENTITY-2044 - Darshanahttps://wso2.org/jira/browse/CARBON-14704 - Ajanthan [1] https://github.com/wso2-dev/carbon4-kernel Thanks, Manoj *Manoj Kumara* Software Engineer WSO2 Inc. http://wso2.com/ *lean.enterprise.middleware* Mobile: +94713448188 On Wed, Feb 19, 2014 at 5:50 PM, Kishanthan Thangarajah <[email protected] > wrote: > > > > On Wed, Feb 19, 2014 at 5:36 PM, Sameera Jayasoma <[email protected]>wrote: > >> Hi Manoj, >> >> Yes we need a patching strategy for Git based Carbon 4 codebase. The >> solution will come into act once the 4.3 release is done. I think we can >> use the existing kernel patching strategy. But we need to figure our a >> proper Git branching mechanism. e.g. maintaining a branch for a kernel >> patch and once the release is done, merge the patch branch with the master. >> > > We can follow the same process we planned other repos/products. The fixes > can be send as pull requests to the kernel dev repo (not to the main repo). > So if some wants to patch kernel, they can do so via this process. Kernel > team will check this pull request and merge it with the dev repo. > > Once we plan on releasing a kernel patch, then we can send these fixes as > pull requests to main repo [1]. When it is successfully merged, we can > create a branch for that patch and do the release. > > >> Sameera. >> >> >> On Tue, Feb 18, 2014 at 10:41 AM, Manoj Kumara <[email protected]> wrote: >> >>> Hi, >>> >>> Since we are now maintaining Carbon 4.x kernel on Git what will be the >>> best way to do the $Subject for . Should we merge the changes at the time >>> of the patch get released as a step of the release process. Otherwise there >>> can be more pull requests if we merge with Git for every kernel fix. >>> >>> WDYT ? >>> >>> >>> [1] https://github.com/wso2/carbon4-kernel >>> >>> >>> *Manoj Kumara* >>> Software Engineer >>> WSO2 Inc. http://wso2.com/ >>> *lean.enterprise.middleware* >>> Mobile: +94713448188 >>> >> >> >> >> -- >> Sameera Jayasoma, >> Architect, >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> blog: http://sameera.adahas.org >> twitter: https://twitter.com/sameerajayasoma >> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections >> Mobile: 0094776364456 >> >> Lean . Enterprise . Middleware >> > > > > -- > *Kishanthan Thangarajah* > Senior Software Engineer, > Platform Technologies Team, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* > Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>* >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
