From: "Warren Togami Jr." <wtogami@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.9rc1 release schedule
Date: Thu, 16 Jan 2014 00:41:37 -1000 [thread overview]
Message-ID: <CAEz79PpC7==Eu4-zq08nQJyEUAbnrTe-ZGVjfDpzmnMi5KZE4g@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJBo7iUEJTfJw2e6qcDmdHNGdDN442Svs5ikVyUL1Jm0Wg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1990 bytes --]
Just a small note of caution for those joining in testing.
https://github.com/bitcoin/bitcoin/issues/3529
Currently the master branch has this issue where leveldb renames all of
.sst files to .ldb. This makes running the 0.8.x version of Bitcoin think
the index is corrupt. Until a fix is included in Bitcoin master, a
workaround to allow 0.8.x to work again is to simply rename all the files
from .ldb back to .sst.
(This workaround worked for me today but failed yesterday. It's possible I
made an error yesterday. If it fails for you please report as we really
need to know if there are other leveldb incompatibilities.)
https://github.com/bitcoin/leveldb/pull/3
The fix for Bitcoin's leveldb is being discussed here.
Warren
On Wed, Jan 15, 2014 at 11:09 PM, Wladimir <laanwj@gmail•com> wrote:
> Hello all,
>
> It has been way to long since last major release. Many improvements and
> new features have been added to master since, so we'd like to do a 0.9rc1
> release soon.
>
> The current aim is next month, February 2014.
>
> Of course there are still some open issues that need to be resolved before
> release
> https://github.com/bitcoin/bitcoin/issues?milestone=12&state=open
>
> If there is something else that you're working on and needs to end up in
> 0.9, or know of some nasty bug in master that should absolutely be solved
> first, please tell.
>
> Wladimir
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 3165 bytes --]
next prev parent reply other threads:[~2014-01-16 10:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 9:09 Wladimir
2014-01-16 10:41 ` Warren Togami Jr. [this message]
2014-01-16 15:23 ` Luke-Jr
2014-01-17 11:44 ` Wladimir
2014-01-17 18:41 ` Luke-Jr
2014-01-17 20:53 ` Jeff Garzik
2014-01-17 21:04 ` Mark Friedenbach
2014-01-18 11:34 ` Jouke Hofman
2014-01-17 21:31 ` Luke-Jr
2014-01-18 8:11 ` Odinn Cyberguerrilla
2014-01-18 11:05 ` Wladimir
2014-01-18 11:28 ` Odinn Cyberguerrilla
2014-01-18 17:38 ` Mark Friedenbach
2014-01-19 2:53 ` Jeff Garzik
2014-01-19 10:24 ` Wladimir
2014-01-23 11:10 ` Wladimir
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='CAEz79PpC7==Eu4-zq08nQJyEUAbnrTe-ZGVjfDpzmnMi5KZE4g@mail.gmail.com' \
--to=wtogami@gmail$(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