From: Kristov Atlas <kristovatlas@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2
Date: Wed, 23 Apr 2014 16:05:49 -0400 [thread overview]
Message-ID: <53581D1D.1000709@gmail.com> (raw)
In-Reply-To: <CAEz79PrAg=yydd3UOk51wGQUWey-KZHUH1Npzwb=qL+6zTj+pQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2396 bytes --]
On 04/22/2014 09:30 AM, Warren Togami Jr. wrote:
> Bitcoin-Translators mailing list is an announce-only mailing list for
> developers to communicate to translators at particular times when new
> translations are needed. Replies and discussion would go to the
> bitcoin dev list. Subscriptions to this list would additionally be
> valuable to the project as it allows for a convenient way to ask for
> translations of other related projects like bitcoin.org
> <http://bitcoin.org> that are hosted on theTransifex platform.
> Whenever source strings of significance are changed or deadlines are
> announced, translators will learn of work to be done in Transifex
> quickly as they will all be subscribed to this announce list.
> Discussion of translation issues should be on the Bitcoin-Development
> list.
>
> Development Roadmap of Bitcoin Core 0.9.2
>
> The Bitcoin Core developers have a desire to do a mostly bug-fix and
> translation update release in v0.9.2. A feature and string freeze will
> start about 3 weeks from now.
>
>
> The purpose of this development roadmap is to communicate the project
> intent and to better organize volunteers. Hopefully doing so will make
> clear when particular types of contributions are most welcome and help
> to push the release process forward in a more timely manner while also
> improving the quality of the release. Missing a target goal is OK.
> The developers may decide to delay particular goals if there are good
> reasons on a case-by-case basis. While schedules may slip, it is
> generally a good thing for a goal to have existed.
>
>
> Schedule (subject to change)
>
> 13 May 2014:Feature freeze. Source string freeze. Release candidate.
>
> 20 May 2014: Testing of a release candidate is roughly a week. More
> time can be added at the discretion of the developers to allow for
> testing if further release candidates are deemed necessary due to
> subsequent changes.
>
>
> Nightly Gitian Builds
>
> https://bitcointalk.org/index.php?topic=571414.0
>
> To make it easier for non-developers and translators to get involved
> in testing unofficial deterministic nightly builds are now available.
>
>
> Warren Togami
I see that the latest nightly build (thanks for that, Warren) is still
not compatible with Tails/Debian Squeeze. Is there still an intention to
address this issue? Might it be fixed by 0.9.2?
[-- Attachment #2: Type: text/html, Size: 5981 bytes --]
next prev parent reply other threads:[~2014-04-23 20:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 13:30 Warren Togami Jr.
2014-04-22 14:05 ` Wladimir
2014-04-23 20:05 ` Kristov Atlas [this message]
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
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=53581D1D.1000709@gmail.com \
--to=kristovatlas@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