1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1QXFVA-00067d-Af
for bitcoin-development@lists.sourceforge.net;
Thu, 16 Jun 2011 16:33:04 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.47 as permitted sender)
client-ip=209.85.160.47; envelope-from=gavinandresen@gmail.com;
helo=mail-pw0-f47.google.com;
Received: from mail-pw0-f47.google.com ([209.85.160.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QXFV9-0006vi-E4
for bitcoin-development@lists.sourceforge.net;
Thu, 16 Jun 2011 16:33:04 +0000
Received: by pwj9 with SMTP id 9so981933pwj.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 16 Jun 2011 09:32:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.231.11 with SMTP id d11mr214314wfh.35.1308241977437; Thu,
16 Jun 2011 09:32:57 -0700 (PDT)
Received: by 10.142.13.1 with HTTP; Thu, 16 Jun 2011 09:32:57 -0700 (PDT)
Date: Thu, 16 Jun 2011 12:32:57 -0400
Message-ID: <BANLkTimZ5j7=1G89uRO9f7fHPdmDMpLMqg@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is freemail (gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.0 RFC_ABUSE_POST Both abuse and postmaster missing on sender domain
0.0 T_TO_NO_BRKTS_FREEMAIL T_TO_NO_BRKTS_FREEMAIL
-0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QXFV9-0006vi-E4
Subject: [Bitcoin-development] Development priorities
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 16:33:04 -0000
Right! I'm back from the CIA, and trying to ignore all the reporters
who want to talk with me.
I want to do a quick brain dump on what I think the short-term
development priorities are. Here's my list:
1) Scaling-up issues, like disconnections when downloading the block chain.
2) Wallet security.
3) Unit testing framework. There was a PULL that had the start of
boost unit tests; I think that is a critical need, along with a good
suite of test cases.
Those are the big issues for me. Anything that slows those down I'm
going to ignore (example: love the idea of escrow transactions, but I
do NOT want to add nifty new features when we're having trouble
keeping the features we're using now working properly).
Does everybody agree those are the critical priorities? (try not to
let this thread wander into a discussion of HOW to do stuff, just WHAT
the priorities aught to be)
--
--
Gavin Andresen
http://clearcoin.com/
|
