From: Wladimir <laanwj@gmail.com>
To: "Warren Togami Jr." <wtogami@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2
Date: Thu, 24 Apr 2014 14:18:51 +0200 [thread overview]
Message-ID: <CA+s+GJDwKzn1X2uR+1uB19+KTpXW+FEOQiWTLcTXJiAJKfdXDA@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJB6Fucjvcve8QQoWdOz=FG-DMJ7z16PLRS2Q_5ReP4o4A@mail.gmail.com>
On Thu, Apr 24, 2014 at 10:25 AM, Wladimir <laanwj@gmail.com> wrote:
> On Thu, Apr 24, 2014 at 10:15 AM, Warren Togami Jr. <wtogami@gmail.com> wrote:
>
> But indeed we need to decide on a cut-off point. I'd have preferred
> 4.7 or 4.8. Qt 4.6 is *ancient* - it was released in februari 2010.
> Apart from tails it doesn't seem like anyone is using those old stable
> distributions on the desktop.
Does anyone know of the timeframe in which tails will switch to a
newer version of Qt?
As it's debian based: will switch to a Wheezy/7.4. Wheezy has Qt 4.8
so is decidedly unproblematic.
I see they're working on migration at least:
- https://tails.boum.org/blueprint/Wheezy/
- https://git-tails.immerda.ch/tails/log/?h=feature/wheezy
Wladimir
next prev parent reply other threads:[~2014-04-24 12:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 13:30 [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2 Warren Togami Jr.
2014-04-22 14:05 ` Wladimir
2014-04-23 20:05 ` Kristov Atlas
2014-04-23 20:28 ` Wladimir
2014-04-23 20:39 ` Warren Togami Jr.
2014-04-23 20:52 ` Kristov Atlas
2014-04-23 22:28 ` Gregory Maxwell
2014-04-24 1:56 ` Kristov Atlas
2014-04-24 8:02 ` Wladimir
2014-04-24 8:07 ` Wladimir
2014-04-24 8:15 ` Warren Togami Jr.
2014-04-24 8:25 ` Wladimir
2014-04-24 12:18 ` Wladimir [this message]
2014-04-25 20:09 ` Kristov Atlas
2014-04-25 20:47 ` 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=CA+s+GJDwKzn1X2uR+1uB19+KTpXW+FEOQiWTLcTXJiAJKfdXDA@mail.gmail.com \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=wtogami@gmail.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