From: Geir Harald Hansen <operator@bitminter•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Version 0.7 release planning
Date: Sat, 11 Aug 2012 18:43:28 +0200 [thread overview]
Message-ID: <50268BB0.8080001@bitminter.com> (raw)
In-Reply-To: <CA+8xBpfeoNOte=GFGqAT7+4U+JCa4DP8CkEupe+oKdJL1dMFFQ@mail.gmail.com>
On 02.08.2012 18:43, Jeff Garzik wrote:
> There seems to be consensus that we should go ahead and do a release,
> before leveldb or ultraprune or anything major lands. There is no
> major landmark feature, but just a useful collection of small changes.
> It seems like a good time to Release Early, Release Often and make a
> checkpoint release.
Looks like much goodness in this version. Thanks for all this work.
Any chance that options to limit the size of blocks and prioritize paid
vs free txes could make it in?
By the way, by far the most common support request I have at my pool is
users withdrawing coins and not seeing it in their wallet because it's
not up-to-date with the block chain. Might be worth adding something in
the bitcoin-qt GUI to make it more obvious that users can't see new
transactions and why.
> 2) Translations update 2012-08-01 (fetched from Transifex)
I just now updated the Norwegian translation on Transifex, if you'd like
to do another pull before the release. For some reason there were many
strings I had already translated that now had no translation and had to
be done again (even ones that had the same English text). Many languages
are now only about 50% translated.
Also there were new duplicated strings:
"Verify a message to ensure it was signed with a specified Bitcoin address"
"Sign a message to prove you own a Bitcoin address"
"Clear &All"
These two seem odd:
Use UPnP to map the listening port (default: 0)
Use UPnP to map the listening port (default: 1 when listening)
Regards,
Geir H. Hansen, bitminter.com
next prev parent reply other threads:[~2012-08-11 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 16:43 Jeff Garzik
2012-08-02 16:45 ` Jeff Garzik
2012-08-02 18:00 ` Gavin
2012-08-02 17:17 ` Luke-Jr
2012-08-11 16:43 ` Geir Harald Hansen [this message]
2012-08-11 18:05 ` Luke-Jr
2012-08-11 18:32 ` Wladimir
2012-08-11 18:56 ` Wladimir
2012-08-12 7:59 ` Geir Harald Hansen
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=50268BB0.8080001@bitminter.com \
--to=operator@bitminter$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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