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.
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
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
