compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (6)

View Page History
* Login using your favorite OpenID provider.

* Go to the [gerrit settings|http://review.couchbase.org/#/settings/] and click on "Agreements" on the left hand side. Contributor agreements are needed for all projects except spymemcached. _Note to *new Couchbase employees*_: you should contact the helpdesk as your process is slightly different.

* While you wait for approval...
* To complete the setup...
** Go through gerrit's Settings screen and set up your SSH keys. _IMPORTANT_: - do not forget to setup your username on the Settings screen.
** Again, the username setup in gerrit \-> Settings \-> SSH Keys ([http://review.couchbase.org/#settings,ssh-keys|http://review.couchbase.org/#settings,ssh-keys]) is important. Folks have been bitten for not doing the username setup while setting up SSH keys.
h1. Initial Project Setup (for each project)

{note}This is not necessary if you intend to use repo. For a repo with membase quick start, please see the README in our [repo manifest|https://github.com/membase/manifest]{note} manifest|https://github.com/couchbase/manifest]{note}

Next, you'll need Change-Id's in all of your commit messages.
h2. Phase 2.5: Rejected\!

If your code was rejected, it's time for a fix and retry: Fix, rebase, repeat (the Change-Id will keep old comments in sync). By the way, don't see a reject as a bad thing. More eyes on a change will usually give it higher quality. It's less effort to fix things before they go in than after they're in a release.

* {{git checkout my-rejected-topic-branch}}
h2. Phase 3: Submit

Once the change is all verified, we can submit. We generally use cherry-pick, which means we need to be a bit careful to do this in order.

Once the submit is complete, the change will automatically show up on github, as we publish changes there too.