From: "Luke-Jr" <luke@dashjr.org>
To: Gavin Andresen <gavinandresen@gmail.com>,
Jeff Garzik <jgarzik@exmulti.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] 0.4.x stable branch
Date: Sun, 18 Sep 2011 19:30:56 -0400 [thread overview]
Message-ID: <201109181930.59565.luke@dashjr.org> (raw)
Gavin, Jeff, et al:
A group of developers would be interested in maintaining 0.4 into the future
as a stable branch (ie, bugfixes only). Would you be willing to plan on making
the next mainline version after 0.4, being called 0.5, so we can release
0.4.1, 0.4.2, etc? If we prepare the git repository + tags, would you guys be
willing to make the actual release builds + source, and/or post such on the
websites you administrate?
Luke and various others in #bitcoin-stable
next reply other threads:[~2011-09-18 23:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 23:30 Luke-Jr [this message]
2011-09-19 12:49 ` [Bitcoin-development] 0.4.x stable branch Gavin Andresen
2011-09-19 13:03 ` Gregory Maxwell
2011-09-19 13:48 ` Amir Taaki
2011-09-19 15:00 ` Luke-Jr
2011-09-19 15:06 ` Gregory Maxwell
2011-09-20 4:41 ` theymos
2011-09-20 19:10 ` Jeff Garzik
2011-09-20 20:37 ` Luke-Jr
2011-09-21 14:24 ` Alex Waters
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=201109181930.59565.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gavinandresen@gmail.com \
--cc=jgarzik@exmulti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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