Skip to content

WIP doc: add Backporting section to SubmittingPatches.rst#22876

Closed
smithfarm wants to merge 1 commit intoceph:masterfrom
smithfarm:wip-sp-backporting
Closed

WIP doc: add Backporting section to SubmittingPatches.rst#22876
smithfarm wants to merge 1 commit intoceph:masterfrom
smithfarm:wip-sp-backporting

Conversation

@smithfarm
Copy link
Contributor

@smithfarm smithfarm commented Jul 5, 2018

  • 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

^^^^^^^^^^^^^^^^^^^^^^^^^^^

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

PR still needs to target master.

.. _`Stable Releases and Backports`: http://tracker.ceph.com/projects/ceph-releases/wiki

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

worth mentioning that this wiki also describes various workflows in the backporting lifecycle

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@jcsp
Copy link
Contributor

jcsp commented Jul 5, 2018

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.

@smithfarm
Copy link
Contributor Author

smithfarm commented Jul 5, 2018

@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
(etc.)

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@smithfarm This is the paragraph (nit) I mentioned in the chat. Dropping that colon nature of your change: would avoid the unnecessary quotation line.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@smithfarm smithfarm force-pushed the wip-sp-backporting branch from 88ec258 to 5cd9d81 Compare July 13, 2018 15:24
@smithfarm
Copy link
Contributor Author

@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:

  • SubmittingPatches-sign-your-commits.rst (just the verbiage regarding signed-off-by)
  • SubmittingPatches-kernel-clients.rst (the rest of the verbiage copied from Linux kernel docs, plus the entire section "Patch submission via ceph-devel")
  • SubmittingPatches-github.rst (instructions for submitting patches targeting master)
  • SubmittingPatches-backporting.rst (the new backporting section)

@tchaikov
Copy link
Contributor

@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/

@jcsp
Copy link
Contributor

jcsp commented Jul 16, 2018

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.

Copy link
Contributor

@LenzGr LenzGr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM except for the minor nit about the capitalization of the backporting headline. Thanks!

you to re-send them using MIME.


BACKPORTING
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest to replace the all-caps headline with "Backporting", to be in line with other headlines in the documentation.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

@smithfarm
Copy link
Contributor Author

Note to self: fix http://tracker.ceph.com/issues/20953 while we're at it.

@smithfarm smithfarm changed the title doc: add Backporting section to SubmittingPatches.rst WIP doc: add Backporting section to SubmittingPatches.rst Jul 20, 2018
@smithfarm smithfarm added the DNM label Jul 20, 2018
@smithfarm smithfarm requested a review from epuertat July 26, 2018 17:58
Signed-off-by: Sage Weil <sage@redhat.com>
(cherry picked from commit ef510e43f0ee14b49e99beed9ae8feda6db3429a)

Conflicts:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may provide some cooked/sample prepare-commit-msg hook like this to uncomment Conflicts section.

@batrick
Copy link
Member

batrick commented Sep 25, 2018

@smithfarm status on this PR?

@stale
Copy link

stale bot commented Nov 24, 2018

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.
If you are a maintainer or core committer, please follow-up on this issue to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

@stale stale bot added the stale label Nov 24, 2018
@smithfarm
Copy link
Contributor Author

Putting this on my to-do list for this coming week.

@stale stale bot removed the stale label Nov 24, 2018
@stale
Copy link

stale bot commented Jan 24, 2019

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.
If you are a maintainer or core committer, please follow-up on this issue to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

@stale stale bot added the stale label Jan 24, 2019
@LenzGr LenzGr removed the backport label Mar 29, 2019
@stale stale bot removed the stale label Mar 29, 2019
@stale
Copy link

stale bot commented Mar 29, 2019

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.
If you are a maintainer or core committer, please follow-up on this issue to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

@stale stale bot added the stale label Mar 29, 2019
@batrick
Copy link
Member

batrick commented Apr 5, 2019

ping @smithfarm

@stale stale bot removed the stale label Apr 5, 2019
@stale
Copy link

stale bot commented Jun 4, 2019

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.
If you are a maintainer or core committer, please follow-up on this pull request to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

@stale stale bot added the stale label Jun 4, 2019
@stale
Copy link

stale bot commented Sep 2, 2019

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!

@stale stale bot closed this Sep 2, 2019
@smithfarm smithfarm reopened this Sep 3, 2019
@stale stale bot removed the stale label Sep 3, 2019
Signed-off-by: Nathan Cutler <ncutler@suse.com>
@smithfarm
Copy link
Contributor Author

closing in favor of #30705

@smithfarm smithfarm closed this Oct 3, 2019
@smithfarm smithfarm deleted the wip-sp-backporting branch October 3, 2019 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants