From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd3Qc-0006ph-Ai for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:05:58 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.192.47 as permitted sender) client-ip=209.85.192.47; envelope-from=kristovatlas@gmail.com; helo=mail-qg0-f47.google.com; Received: from mail-qg0-f47.google.com ([209.85.192.47]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wd3Qb-0001p9-7h for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:05:58 +0000 Received: by mail-qg0-f47.google.com with SMTP id e89so1538323qgf.34 for ; Wed, 23 Apr 2014 13:05:51 -0700 (PDT) X-Received: by 10.140.93.198 with SMTP id d64mr63900374qge.1.1398283551654; Wed, 23 Apr 2014 13:05:51 -0700 (PDT) Received: from [10.0.2.15] (c-50-191-76-100.hsd1.pa.comcast.net. [50.191.76.100]) by mx.google.com with ESMTPSA id s13sm3509999qag.19.2014.04.23.13.05.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Apr 2014 13:05:50 -0700 (PDT) Message-ID: <53581D1D.1000709@gmail.com> Date: Wed, 23 Apr 2014 16:05:49 -0400 From: Kristov Atlas User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------050502050406080603010201" X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (kristovatlas[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [209.85.192.47 listed in list.dnswl.org] 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Wd3Qb-0001p9-7h Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Apr 2014 20:05:58 -0000 This is a multi-part message in MIME format. --------------050502050406080603010201 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 > 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? --------------050502050406080603010201 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 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? --------------050502050406080603010201--