mirror of
https://github.com/ceph/ceph
synced 2024-12-28 14:34:13 +00:00
e12ac2ddd1
Before this commit, one had to go through the releases index to get to the main releases page. This should be the other way around. Also, the main releases page should not be called "schedule.rst" - while it contains a release timeline, that's not its principal purpose. Rename the page to "general.rst" and move the "Understanding the release cycle" section before the timeline. Signed-off-by: Nathan Cutler <ncutler@suse.com>
37 lines
1.1 KiB
ReStructuredText
37 lines
1.1 KiB
ReStructuredText
Notes on Ceph repositories
|
|
==========================
|
|
|
|
Special branches
|
|
----------------
|
|
|
|
* ``master``: current tip (integration branch)
|
|
* Release branches (for example ``luminous``) corresponding to the releases
|
|
listed at :ref:`ceph-releases-index`
|
|
|
|
Rules
|
|
-----
|
|
|
|
The source repos are all on github.
|
|
|
|
* Any branch pushed to ceph-ci.git will kick off builds that will
|
|
generate packages and repositories on shaman.ceph.com. Try
|
|
not to generate unnecessary load. For private, unreviewed work,
|
|
only push to branches named ``wip-*``. This avoids colliding with
|
|
any special branches.
|
|
|
|
* Nothing should reach a special branch unless it has been
|
|
reviewed.
|
|
|
|
* Preferred means of review is via github pull requests to capture any
|
|
review discussion.
|
|
|
|
* For multi-patch series, the pull request can be merged via github,
|
|
and a Reviewed-by: ... line added to the merge commit.
|
|
|
|
* For single- (or few-) patch merges, it is preferable to add the
|
|
Reviewed-by: directly to the commit so that it is also visible when
|
|
the patch is cherry-picked for backports.
|
|
|
|
* All backports should use ``git cherry-pick -x`` to capture which
|
|
commit they are cherry-picking from.
|