Hello, We've recently changed a bit how tarantool branches are organized and branch layout itself:
1) tarantool.git on "farm" from now on is a complete mirror of the public repository at github.com/mailru/tarantool. Every branch pushed into tarantool.git is immediately propagated to github with a post-update trigger. "unstable" branch was removed, and all contents of this branch was merged into "master". Please do not recreate "unstable" again! 2) All new development, unless otherwise requested, should be based on "master" branch in tarantool. There will be no more "unstable" branch, thus please base your new feature on the "master" mainline. We'll have integration windows once in a few months when new features are allowed to be pushed into "master" mainline. All bugfixes can and should go into master at any time. 3) We're adding peer review process for all patches that go into master. Please send your patches to [email protected] or tarantool-private to get a peer review before a push into master/master_private. Before a feature or bug can be pushed it should be peer-reviewed! 4) For company-private development, a separate repository was created on farm, called tarantool_private. Please use this repository for all company-private development. Careful: the mainline "master" branch in tarnatool_private is called master_private. Please never push from tarantool_private to tarantool. A good practice is to have two separate directories for private and public repositories, rather than have multiple remotes in the same repository, to avoid pushing a branch to a wrong repository by mistake. Patches for private features should be sent to tarantool-private company mailinig list for review. Thanks, -- _______________________________________________ Mailing list: https://launchpad.net/~tarantool-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~tarantool-developers More help : https://help.launchpad.net/ListHelp
