WIP doc: add Backporting section to SubmittingPatches.rst#22876
WIP doc: add Backporting section to SubmittingPatches.rst#22876smithfarm wants to merge 1 commit intoceph:masterfrom
Conversation
SubmittingPatches.rst
Outdated
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| If you want to stage the backport yourself, first find out the backport tracker | ||
| number of the fix (see `Backport tracking`_, above) by referring to the |
There was a problem hiding this comment.
I don't see the part that describes how the Backport tracker item is created. (I'm unsure how these are created mysefl! Is there a script that does this?)
There was a problem hiding this comment.
Yes, the script is here: https://github.com/ceph/ceph/blob/master/src/script/backport-create-issue
I did not mention it on purpose because I didn't want to encumber SubmittingPatches.rst with Too Much Information, especially seeing as new contributors typically do not have sufficient tracker permissions to run the script.
But I agree this information should be presented somewhere. Here?
SubmittingPatches.rst
Outdated
| PR still needs to target master. | ||
|
|
||
| .. _`Stable Releases and Backports`: http://tracker.ceph.com/projects/ceph-releases/wiki | ||
|
|
There was a problem hiding this comment.
worth mentioning that this wiki also describes various workflows in the backporting lifecycle
|
This all looks good to me -- I wonder if now is a good time to think about breaking this up into a few different pages? The longer SubmittingPatches.rst gets, the more someone might skip reading it. I'm happy to have a go at that in a separate PR after this though. |
|
@jcsp Thanks for looking. I hear you about the document getting long. It's nice to have it all in one place, though. I get the feeling that some folks only read the document after being pointed to it, and it's easy to point them to the relevant section via links. For example, if someone needs to be "convinced" to add "Signed-off-by", point them to https://github.com/ceph/ceph/blob/master/SubmittingPatches.rst#1-sign-your-work |
SubmittingPatches.rst
Outdated
| branches (for example, the "hammer" or "infernalis" branches), your initial | ||
| PR should still target the master branch. Please see the `BACKPORTING`_ | ||
| section, below, for information on how to ensure your bugfix gets | ||
| backported. |
There was a problem hiding this comment.
@smithfarm This is the paragraph (nit) I mentioned in the chat. Dropping that colon nature of your change: would avoid the unnecessary quotation line.
88ec258 to
5cd9d81
Compare
|
@jcsp I'll tackle splitting the file into a number of smaller files. What kind of structure would you suggest? I'm envisioning something like this:
|
|
@smithfarm i'd suggest have "SubmittingPatches-sign-your-commits.rst" and "SubmittingPatches-github.rst" in a single file. also, how about creating a template for PR? see https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/ |
|
I agree with @tchaikov that the basic signing and basic PR instructions should go together. It's a good idea to put the kernel patch info and the backporting info on separate pages as you suggest, as most new contributors don't touch them. I would suggest making the first thing on the main page with an example commit message: this is the part that people most often miss, even if they are familiar with how to use github. |
LenzGr
left a comment
There was a problem hiding this comment.
LGTM except for the minor nit about the capitalization of the backporting headline. Thanks!
SubmittingPatches.rst
Outdated
| you to re-send them using MIME. | ||
|
|
||
|
|
||
| BACKPORTING |
There was a problem hiding this comment.
I'd suggest to replace the all-caps headline with "Backporting", to be in line with other headlines in the documentation.
There was a problem hiding this comment.
@LenzGr All the headlines at this level are in all-caps, actually, but (a) we're talking about breaking this up into separate documents, and (b) I agree that all-caps headlines are undesirable, so I'll keep that in mind for the next round of revisions.
|
Note to self: fix http://tracker.ceph.com/issues/20953 while we're at it. |
SubmittingPatches.rst
Outdated
| Signed-off-by: Sage Weil <sage@redhat.com> | ||
| (cherry picked from commit ef510e43f0ee14b49e99beed9ae8feda6db3429a) | ||
|
|
||
| Conflicts: |
There was a problem hiding this comment.
We may provide some cooked/sample prepare-commit-msg hook like this to uncomment Conflicts section.
|
@smithfarm status on this PR? |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
Putting this on my to-do list for this coming week. |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
ping @smithfarm |
|
This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days. |
|
This pull request has been automatically closed because there has been no activity for 90 days. Please feel free to reopen this pull request (or open a new one) if the proposed change is still appropriate. Thank you for your contribution! |
Signed-off-by: Nathan Cutler <ncutler@suse.com>
3db174f to
6d04384
Compare
|
closing in favor of #30705 |
SubmittingPatches.rst(general guidelines, for GitHub/master branch)SubmittingPatches-kernel.rst(for kernel patches)SubmittingPatches-backports.rst(for backports)Fixes: http://tracker.ceph.com/issues/20953