Willem, a big thank! I've just sow the job on the internal repo, you made a very quick and deep review! So the github pull req will never be merged, right? Any suggestion for a better contribution procedure is welcome. Cheers, Carlo
2014-05-28 16:53 GMT+02:00 Willem Jiang <[email protected]>: > Hi Carlo, > > I already merged the PR 158 into apache camel. > Current we do the patch release per 6 or 8 weeks. > As we just released Camel 2.13.1 two weeks ago, you PR should be part of > camel-2.13.2 at the end of next month. > > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > On May 28, 2014 at 10:07:06 PM, carlo cancellieri ( > [email protected]) wrote: > > Hi all, > > I've 2 important questions to understand how to proceed. > > > > I'm working on a new huge project and I'm going to port many spring-batch > > based jobs to camel. > > > > I need to sync our release and spring schedule with the camel one so we > can > > contribute to the project and get the improvements ready for our new > tags. > > > > Are there any release scheduling pages? Do you use a fixed time box > release > > or what? > > > > Could you kindly consider to merge this pull req before the next release? > > > > https://issues.apache.org/jira/browse/CAMEL-7450 > > > > https://github.com/apache/camel/pull/158 > > > > Cheers, > > Carlo > > > > -- > > Dott. Carlo Cancellieri > > *skype*: ccancellieri > > *Twitter*: @cancellieric > > *LinkedIn*: http://it.linkedin.com/in/ccancellieri/ > > > > -- Dott. Carlo Cancellieri *skype*: ccancellieri *Twitter*: @cancellieric *LinkedIn*: http://it.linkedin.com/in/ccancellieri/
