On Wednesday, June 20, 2012 9:40:56 PM UTC-7, rajiv wrote: > > We would like to contribute these changes back to the 1.6 branch. Can > someone tell me or point me to info on the process to do that? Is it is > multi step process where I first need to upload the entire 1.6 version that > we have with the new code and then later after some review we integrate our > changes into the 1.6 mainline? Or do I have to download lthe latest 1.6 > branch, port our changes to it and post that? Also where (URL) is it that > I would upload the version/changes that I have? >
Sorry to be responding late here, but the best way to contribute a new storage mechanism to 1.6 is to do it entirely outside of the memcached tree and operate it as a separate project. The engine branch isn't done if someone to modify the core for the engine to work. A few of us have taken it really really far, so I would be surprised if your engines had needs the interface couldn't cover, but it's certainly possible. Obviously, work that you do such as thread affinity that changes the core is done using a fairly standard git flow (fork the project, send your changes for review, revise, repeat, etc...).
