[BTC-dev] UPDATED v0.0.2: Creating, Naming, and Submitting a Vpatch

[Shane Kinney]

URL: <http://therealbitcoin.org/ml/btc-dev/attachments/20150928/attachment_8609a5f7691b090b0f5531bc312f966eb9a3b707.txt>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

..::[ The Bitcoin Foundation: Creating, Naming And Submitting A Vpatch ]::..

    [                   Date: 2015.09.04                               ]
    [                Version: 0.0.3                                    ]
    [                 Author: mod6 [R.01]                              ]

Introduction]:
      With the recent implementation of `V' [R.02] by asciilifeform [R.03] this
      document requires a third revision to ensure a consistant methodology for
      creating, naming and submitting a vpatch.

0x00] Creating the Patch:

      With all of the signed vpatches from The Bitcoin Foundation applied via
      `V', follow these next steps to copy over the `pressed' source so you
      can make the changes for your patch and then output the vpatch of the
      changes with `vdiff.sh' [R.04].

      mkdir -p a b
      cp -pr bitcoin a && cp -pr bitcoin b

      Now that you have the patched source copied into ``a'' and ``b'':

      cd b

      Now you should make your changes to the code as necessary.

0x01] Naming and Numbering the Vpatch:

      Once the code changes are complete, create a vdiff of the changes:

      vdiff.sh a b > patchname.vpatch

      [ Example ]:
      vdiff.sh a b > mod6_fix_dumpblock_params.vpatch

0x02] Signing the Patch:

      The Bitcoin Foundation requires that you use a GnuPG Detached Signature
      to sign your vpatch file.

      For your submitted vpatch to work with `V', sign the vpatch exactly file
      as follows:

      gpg --armor --output <vpatch_name>.vpatch.<wot_uid>.sig \
      --detach-sig <vpatch_name>.vpatch

      [ Example ]:
      gpg --armor --output mod6_fix_dumpblock_params.vpatch.mod6.sig \
      --detach-sig mod6_fix_dumpblock_params.vpatch

0x03] Submitting the Patch

      To send your patch(s) to the BTC-Dev [R.05] mailing list, first you need
      to create a GPG signed message and then attach your vpatch file(s) and
      your detached signature files to the email.  Also, create a clear-signed
      message detailing vpatch(s) contained in the submission.

      The BTC-dev [R.05] mailing list won't broadcast messages that aren't GPG
      signed with a GPG key in the #bitcoin-assets WoT [R.06].  Your submission
      must be signed with a key that has positive ratings with respect to
      `assbot`'s L2 [R.07].

[ References ]:

  [R.01]: 027A 8D7C 0FB8 A166 4372 0F40 7217 05A8 B71E ADAF
  [R.02]: http://therealbitcoin.org/ml/btc-dev/2015-August/000160.html
  [R.03]: 1721 5D11 8B72 3950 7FAF ED98 B982 28A0 01AB FFC7
  [R.04]: http://deedbot.org/deed-372115-1.txt
  [R.05]: http://thebitcoin.foundation/mailman/listinfo/btc-dev
  [R.06]: http://www.btcalpha.com/wot/
  [R.07]: http://www.btcalpha.com/wot/user/assbot/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iQIcBAEBCgAGBQJWCdW5AAoJEHIXBai3Hq2vVEAP+wSHsdeZSA67gfAsI0Wflijl
teWdHMdxJmMANXbD79s+WUqvhNpGmeomMUiRKJmOnFYZnaK3PhWx68LT/nu6A9R5
0qfyHGWGomwncPz/r6mwNUVLzcO143GoDWdtC+akJpW7LIZhNdrNOuS1EAzsopS0
6KMC43Yfq+qwS9GA/WuWnExWW4YwAz5MAc599ROxikmlkiFFzJbFKafwFebjXrJ6
mfOlL1l7ipafSR1Dbl/JJMfmg6OpyFYGDIG3yeJa//VJaPcFRUraooooLoXcbi3u
T/5Fb0DJR94f+LWmz5dHbxFvznJPm1m73XZDqqBAarejeI91Ro5DN1wnddhz2lhA
+87WTtwOLanxugw4gFmmv76noanU7hM8e4W370SdPdXUj/aV1VsQ1x+hto87JdNn
EFXLF9JHAzqbjLHuTNClPvxJAXKn+KnjAd+XVumnLxVjTfD0huph3UpxASH0rCNU
Ep71OOC0u8mZHrsMYkhaiD6+rAawsBj3M0EScDbnx0TzTxl/4KPzBrWEspN9JhKw
PFl2lEWdfCOxBwiJX8yyrJpJWI60Vi7RukJhZb6+IANHcMw93anKbQfY0kf8o7ff
M5CIjhWRmBZ457DXSoW0HFChnrAeKETb64W87/+SQjC+kXSzOfomt2l6k4lRSxfi
9/gYQXm4HJl9OTg0ZEwI
=uli6
-----END PGP SIGNATURE-----