summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGavin Andresen <gavinandresen@gmail.com>2012-11-06 13:47:34 -0500
committerbitcoindev <bitcoindev@gnusha.org>2012-11-06 18:47:41 +0000
commit51bec4e75fdece7133ad57cca2d08c608cd3f943 (patch)
tree33a1da95ee1416480da1c53e67a56be981754516
parentcf11c021c821404d98895536551f7f4577cd7f81 (diff)
downloadpi-bitcoindev-51bec4e75fdece7133ad57cca2d08c608cd3f943.tar.gz
pi-bitcoindev-51bec4e75fdece7133ad57cca2d08c608cd3f943.zip
[Bitcoin-development] IRC meeting agenda, 18:00 UTC Thursday
-rw-r--r--ad/83a11332ecc48803a54e291db181c1ed067eb277
1 files changed, 77 insertions, 0 deletions
diff --git a/ad/83a11332ecc48803a54e291db181c1ed067eb2 b/ad/83a11332ecc48803a54e291db181c1ed067eb2
new file mode 100644
index 000000000..423d6caca
--- /dev/null
+++ b/ad/83a11332ecc48803a54e291db181c1ed067eb2
@@ -0,0 +1,77 @@
+Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
+ helo=mx.sourceforge.net)
+ by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <gavinandresen@gmail.com>) id 1TVoBZ-0006mZ-FW
+ for bitcoin-development@lists.sourceforge.net;
+ Tue, 06 Nov 2012 18:47:41 +0000
+Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
+ designates 209.85.212.175 as permitted sender)
+ client-ip=209.85.212.175; envelope-from=gavinandresen@gmail.com;
+ helo=mail-wi0-f175.google.com;
+Received: from mail-wi0-f175.google.com ([209.85.212.175])
+ by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1TVoBY-0000AM-OY
+ for bitcoin-development@lists.sourceforge.net;
+ Tue, 06 Nov 2012 18:47:41 +0000
+Received: by mail-wi0-f175.google.com with SMTP id hq4so3536368wib.10
+ for <bitcoin-development@lists.sourceforge.net>;
+ Tue, 06 Nov 2012 10:47:34 -0800 (PST)
+MIME-Version: 1.0
+Received: by 10.181.11.167 with SMTP id ej7mr3819283wid.11.1352227654667; Tue,
+ 06 Nov 2012 10:47:34 -0800 (PST)
+Received: by 10.194.27.136 with HTTP; Tue, 6 Nov 2012 10:47:34 -0800 (PST)
+Date: Tue, 6 Nov 2012 13:47:34 -0500
+Message-ID: <CABsx9T1K+XKr=OT5TC4d1KiQ_kXH+giCWHPiS=t7-NyVOmGTDw@mail.gmail.com>
+From: Gavin Andresen <gavinandresen@gmail.com>
+To: Bitcoin Dev <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 commonly abused enduser mail provider
+ (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
+X-Headers-End: 1TVoBY-0000AM-OY
+Subject: [Bitcoin-development] IRC meeting agenda, 18:00 UTC Thursday
+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: Tue, 06 Nov 2012 18:47:41 -0000
+
+Thursdays at 18:00 UTC (6PM Europe/1PM east US/10AM west US) seem to
+be a good time for the core dev team to meet on the #bitcoin-dev
+freenode IRC channel to chat.
+
+I'd like to talk about:
+
+o Can we put together a TODO list to get to a 0.8 release candidate ?
+
+o Is it time to feature-freeze 0.8 and work on just testing the new
+features and fixing existing bugs (the issues list keeps getting
+longer and longer ... )?
+
+o BIP process: are we happy with how it is working? What can we do to
+improve it?
+
+What else should we talk about?
+
+--
+--
+Gavin Andresen
+
+