1 Notes on Ceph repositories
2 ==========================
7 * ``master``: current tip (integration branch)
8 * ``next``: pending release (feature frozen, bugfixes only)
9 * ``last``: last/previous release
10 * ``dumpling``, ``cuttlefish``, ``bobtail``, ``argonaut``, etc.: stable release branches
11 * ``dumpling-next``: backports for stable release, pending testing
16 The source repos are all on github.
18 * Any branch pushed to ceph.git will kick off builds that will either
19 run unit tests or generate packages for gitbuilder.ceph.com. Try
20 not to generate unnecessary load. For private, unreviewed work,
21 only push to branches named ``wip-*``. This avoids colliding with
24 * Nothing should every reach a special branch unless it has been
27 * Preferred means of review is via github pull requests to capture any
30 * For multi-patch series, the pull request can be merged via github,
31 and a Reviewed-by: ... line added to the merge commit.
33 * For single- (or few-) patch merges, it is preferable to add the
34 Reviewed-by: directly to the commit so that it is also visible when
35 the patch is cherry-picked for backports.
37 * All backports should use ``git cherry-pick -x`` to capture which
38 commit they are cherry-picking from.