From: Daniel Stadulis <dstadulis@gmail•com>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] 2015-10-01 #bitcoin-dev Weekly Development Meeting Minutes
Date: Fri, 2 Oct 2015 01:06:22 -0700 [thread overview]
Message-ID: <CAHpxFbGy5T4ONV8qJeUoQeSK0b9iz34xK8+vRXMOLoYsvXLZBA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
Meeting Title:
#bitcoin-dev Weekly Development Meeting
Meeting Date:
2015-10-01
Meeting Time:
19:00-20:00 UTC
Participants in Attendance:
dstadulis
wumpus
morcos
gmaxwell
btcdrak
jonasshnelli
maaku
sdaftuar
sipa
BlueMatt
CodeShark
Luke-Jr
bsm117532
jgarzik
IRC Chat Logs:
http://bitcoinstats.com/irc/bitcoin-dev/logs/2015/10/01#l1443726030.0
----------------------------
Topics Discussed:
1.) Mempool limiting
2.) BIP68 + CHECKSEQUENCEVERIFY
3.) CLTV soft fork deployment
4.) libconsensus merge time window
4.1) Agreement there should be a merge window for move-only changes
4.2)jtimon will document higher-level rationales for moves, so people can
first agree on what should move where
----------------------------
2015-10-01 Meeting Conclusions:
#
Action items
Responsible Parties
Due Date/ETA
1
Mempool limiting:
BlueMatt: to finish 6722 code.
Others:Try attacking 6722, 6557, and 6673 to see edge-case behavior
BlueMatt et al
Undetermined due date
2
morcos email dev list with chain-limit proposal, sdaftuar will review
proposal before list is emailed
morcos & sdaftuar
Undetermined due date
3
CLTV backport PRs #6706 and #6707 (backport 0.10 and 0.11 respectively)
need review ASAP
All
ASAP
4
Need reviews/ACKs of
BIP68 #6312,
BIP112 CSV #6564,
BIP113 #6566
All
By 2015-10-08
5
Document higher-level rationales for libconsensus moves, so people can
first agree on what should move where
jtimon
Undetermined due date
[-- Attachment #2: Type: text/html, Size: 2469 bytes --]
reply other threads:[~2015-10-02 8:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHpxFbGy5T4ONV8qJeUoQeSK0b9iz34xK8+vRXMOLoYsvXLZBA@mail.gmail.com \
--to=dstadulis@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox