rust-bitcoin / rust-bitcoin / 8764734482 / 1

83%

master: 83%

push

github

Merge rust-bitcoin/rust-bitcoin#2685: Add backport section to contributing docs

<a class=hub.com/rust-bitcoin/rust-bitcoin/commit/<a class="double-link" href="https://git"><a class=hub.com/rust-bitcoin/rust-bitcoin/commit/<a class="double-link" href="https://git"><a class=hub.com/rust-bitcoin/rust-bitcoin/commit/b49e6707726b84f0c3bae19be43b447e3392a596">b49e67077 Add backport section to contributing docs (Tobin C. Harding)

Pull request description:

  Add a section on how we do backports and what the merge policy is.

  Recently I backported a patch by pushing directly to the `0.32.x` release branch but this is not an optimal process because it leaves no history on github. Instead PR backports in like we do for patching `master` but allow one-ACK merging if the backport is a straight cherry pick of a patch from `master`.

ACKs for top commit:
  apoelstra:
    ACK b49e6707726b84f0c3bae19be43b447e3392a596 looks much better!
  storopoli:
    ACK b49e6707726b84f0c3bae19be43b447e3392a596
  sanket1729:
    ACK b49e6707726b84f0c3bae19be43b447e3392a596

Tree-SHA512: f114cc015bd503f58f2ac48d7396cbe131b

19195 of 23090 relevant lines covered (83.13%)

16721.79 hits per line