[BTC-dev] November 2014 ToDo List
Shane Kinney
modsix at gmail.com
Wed Nov 12 05:17:05 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
..::[ BTC Foundation TODO List: November 2014 ]::..
0x0]: Need to build v0.5.3 with the following patches and test if it will
compile with the posted patches individually.
0x0A: chicken.tar.gz [asciilifeform] [R.2]
0x0B: rm_rf_upnp.tar.gz [ben_vulpes] [R.3]
0x0C: https-snipsnip.tar.gz [asciilifeform] [R.2]
0x0D: turdmeister-alert-snip.tar.gz [asciilifeform] [R.2]
0x0E: goodbye-win32.tar.gz [asciilifeform] [R.2]
0x0F: reward_overflow.tar.gz [dignork] [R.4]
Notes: Once it is verified that each tarball above (0x0A-0x0F) is
patched into a clean v0.5.3 and compiles, do some further
debugging and analysis for overall impact. Some of these
patches introduce large changes to the codebase, care must
be taken to ensure no regressions or defects have been
introduced.
If the first condition is satisfied for patches (0x0A-0x0F),
start with a clean v0.5.3 and add each patch in succession
to ensure the patches will build cleanly, together. If
successful, do analysis and debugging to ensure no regressions
or defects have been introduced.
This process may seem a bit redundant, but Bad Things(TM) can
happen while patching and when major code is being cut from
the existing code base. Better to measure twice and cut once.
0x1]: In reference to [R.1]
Attempt to do the following in the following order:
0x1A: ``reproduce 0.5.3 wedging at block 252450''
0x1B: ``determine why 0.5.3 sticks where it does''
0x2]: Summary
The goal is to have what is outlined in 0x0 & 0x1 complete by the end
of November 2014. Much caution will be taken in the entire endevour,
and there is much work to be done. We believe our goal will for 0x0
will be met by the end of the month.
The monthly STATE OF BITCOIN address will provide updates on progress
of our current goals, problems encountered, and future steps.
[ Announcement ]:
Your contributions are welcomed in the form of patches to the
reference implementation; however, going forward we request that you
appropriately name your tarballs and contained files. We leave this
to your best judgement.
Note the following nomenclature:
bitcoin-v<MAJ_MIN_MAINT>-<succinct_patchname>.tar.gz
For example:
bitcoin-v0_5_3-qt_removed.tar.gz
Also, if your patch is in direct reference to a specific
commit id, feel free to also include it in the name:
For example:
bitcoin-v0_5_3-123abc456_qt_removed.tar.gz
If patches do not come in this form or have ambiguous names without
reference to the version number of which to be applied, they will be
ignored.
Thank you, your efforts are very much appreciated.
[ References ]:
[R.1] http://wiki.bitcoin-assets.com/0.5.3-todos
[R.2] 1721 5D11 8B72 3950 7FAF ED98 B982 28A0 01AB FFC7
[R.3] 4F79 0794 2CA8 B89B 01E2 5A76 2AFA 1A9F D2D0 31DA
[R.4] C333 0E59 5A36 9D17 A9FF FCFE 8334 BB7B 5BDF A126
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (FreeBSD)
iQIcBAEBCgAGBQJUYurEAAoJEHIXBai3Hq2v0EUQAJMW6W0wbDYmU202guF9dQ9O
xFk4+lbtcV86aAk/R2At+pfeaJuc/STBH+C1TfwWuUStE88WBD+/9XvHeKwvO6kN
HzRsmVCcJqsl8RP0v4wnwe+T76eWhIPSUbLZt1l6Oz8g+c4T9BDBuV1a3sl770G4
AIxRtCeEcsWeaAs+lsV0v+8jL9luDTrK1f0e22YExKpTc1lgPU+9eC2v4u0bEsM6
X3Ltj1RAYYP7cXM6EBehNcbdbxkzEI9as2dCVsulaMn6T7h0D+Nrguo3Elr9FdyJ
RyA+tBqICk8NilysGjLfGfnA4ZN1Tukxr61uIL3NyZrMRMrWyjHpaaEtIPrhiEBX
Mm8pIutgETyYmCuoEJjO2pn4P419wwdEcwd0l7yIgXORI+rZF/a2GwISm55oam1J
MUMfoHAvDDNIx11Up69Xo+Q6Z06CmfoGZJRWC0l94efPC0yuzHDrpAPsQshBHhqc
K0HR3EpSEaU9/Ga147GOSOdsipq3NxRWbE9yEx/OK8wLT007LlPSATuSDz6w02V9
XxxxQzPhLyJkAy/MceAC9c4PD60WRQWrjmS83FJXEElPsIlb6WrBv1b6XLlfRNty
x59xrxsJ+LhFCfaJbcGYHO1/RuddlZRUPTqLmmle+VCL+4bhTeLCUHoxjNF9xmw3
B2g6x28TcuoeyR+vOtEK
=Rcqi
-----END PGP SIGNATURE-----
More information about the BTC-dev
mailing list