summaryrefslogtreecommitdiff
path: root/3c/d63df5ce6ebf056bb181d033765a4023b17891
blob: bffc40d17bfa3e8e7dca77b8ef4a46de336d4bc7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <wtogami@gmail.com>) id 1WcamD-0002fi-8E
	for bitcoin-development@lists.sourceforge.net;
	Tue, 22 Apr 2014 13:30:21 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.160.169 as permitted sender)
	client-ip=209.85.160.169; envelope-from=wtogami@gmail.com;
	helo=mail-yk0-f169.google.com; 
Received: from mail-yk0-f169.google.com ([209.85.160.169])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Wcam7-0002fp-Uo
	for bitcoin-development@lists.sourceforge.net;
	Tue, 22 Apr 2014 13:30:21 +0000
Received: by mail-yk0-f169.google.com with SMTP id 142so4617372ykq.28
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 22 Apr 2014 06:30:10 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.36.16 with SMTP id v16mr1883837yha.153.1398173404193;
	Tue, 22 Apr 2014 06:30:04 -0700 (PDT)
Received: by 10.170.58.146 with HTTP; Tue, 22 Apr 2014 06:30:04 -0700 (PDT)
Date: Tue, 22 Apr 2014 03:30:04 -1000
Message-ID: <CAEz79PrAg=yydd3UOk51wGQUWey-KZHUH1Npzwb=qL+6zTj+pQ@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e0160b12818451804f7a19d32
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
	(wtogami[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	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: 1Wcam7-0002fp-Uo
Subject: [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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 13:30:21 -0000

--089e0160b12818451804f7a19d32
Content-Type: text/plain; charset=UTF-8

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.

Translation of Bitcoin Core

https://www.transifex.com/projects/p/bitcoin/

Transifex allows open source projects a convenient way to coordinate the
work of many translators.  Periodically English language source strings
from Bitcoin Core are synchronized to the Transifex project.  Those strings
are then translated in the convenient Transifex web interface where
contributors are able to join by creating a free account.  Senior
contributors can be promoted to a Reviewer or Maintainer role for each
language.  Developers pull from Transifex to merge translated strings back
into Bitcoin Core. As a matter of policy translations are NOT accepted via
Github pull requests as those changes would be overwritten by the next
Transifex pull and there is no clean way to keep them in sync when changes
are made in both places.

https://github.com/bitcoin/bitcoin/blob/master/doc/translation_process.md

The latest version of the Translation process can be found here.

Bitcoin-Translators Announce-only List

https://groups.google.com/forum/#!forum/bitcoin-translators
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.

Other Improvements to the Translation process

   -

   Prior to an intended release a String Freeze is declared on a particular
   date.  The string freeze exists to ensure that translators have a
   reasonable amount of time to translate new or modified source strings so
   their work can be included in a release.
   -

   A significant issue with our past translation process was the lack of
   branch support in Transifex.  This meant that since master and v0.8.2
   diverged in May 2013, translation updates made in Transifex were not
   included in the v0.8.x stable releases until the release of v0.9.0 in early
   2014.  v0.9.1 similarly was released from a branch outside from master.
    v0.9.2 is planned to be released directly from the master branch so
   translations for this upcoming release can be developed directly.  laanwj
   came up with a great idea for dealing with future releases where we will be
   able to keep translations for both diverged stable and master branch
   simultaneously in Transifex, with scripts automating the process of merging
   strings and separating them back to the diverged branches.


Please post questions or comments about the release or translation process
here on Bitcoin-Development list. Bug reports should be posted a Github
Issues<https://github.com/bitcoin/bitcoin/issues?direction=desc&sort=updated&state=open>tickets.

Warren Togami

--089e0160b12818451804f7a19d32
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span id=3D"docs-internal-guid-ac88c82a-899b-a837-487c-ff6=
be988c0f5"><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-b=
ottom:0pt"><span style=3D"font-size:15px;font-family:Arial;font-weight:bold=
;vertical-align:baseline;white-space:pre-wrap">Development Roadmap of Bitco=
in Core 0.9.2</span></p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline;whi=
te-space:pre-wrap">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 fre=
eze will start about 3 weeks from now.</span></p>
<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt"><span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline=
;white-space:pre-wrap">The purpose of this development roadmap is to commun=
icate 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. =C2=A0Missing a target goal is =
OK. The developers may decide to delay particular goals if there are good r=
easons on a case-by-case basis. While schedules may slip, it is generally a=
 good thing for a goal to have existed.</span></p>
<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt"><span style=3D"font-size:15px;font-family:Arial;font-weight:bold;vertic=
al-align:baseline;white-space:pre-wrap">Schedule (subject to change)</span>=
</p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline;whi=
te-space:pre-wrap">13 May 2014:</span><span style=3D"font-size:15px;font-fa=
mily:Arial;font-weight:bold;vertical-align:baseline;white-space:pre-wrap"> =
</span><span style=3D"font-size:15px;font-family:Arial;vertical-align:basel=
ine;white-space:pre-wrap">Feature freeze. =C2=A0Source string freeze. =C2=
=A0Release candidate.</span></p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline;whi=
te-space:pre-wrap">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 subse=
quent changes.</span></p>
<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt"><span style=3D"font-size:15px;font-family:Arial;font-weight:bold;vertic=
al-align:baseline;white-space:pre-wrap">Nightly Gitian Builds</span></p><p =
dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">
<a href=3D"https://bitcointalk.org/index.php?topic=3D571414.0" style=3D"tex=
t-decoration:none"><span style=3D"font-size:15px;font-family:Arial;text-dec=
oration:underline;vertical-align:baseline;white-space:pre-wrap">https://bit=
cointalk.org/index.php?topic=3D571414.0</span></a></p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline;whi=
te-space:pre-wrap">To make it easier for non-developers and translators to =
get involved in testing unofficial deterministic nightly builds are now ava=
ilable.</span></p>
<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt"><span style=3D"font-size:15px;font-family:Arial;font-weight:bold;vertic=
al-align:baseline;white-space:pre-wrap">Translation of Bitcoin Core</span><=
/p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<a href=3D"https://www.transifex.com/projects/p/bitcoin/" style=3D"text-dec=
oration:none"><span style=3D"font-size:15px;font-family:Arial;text-decorati=
on:underline;vertical-align:baseline;white-space:pre-wrap">https://www.tran=
sifex.com/projects/p/bitcoin/</span></a></p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline;whi=
te-space:pre-wrap">Transifex allows open source projects a convenient way t=
o coordinate the work of many translators. =C2=A0Periodically English langu=
age source strings from Bitcoin Core are synchronized to the Transifex proj=
ect. =C2=A0Those strings are then translated in the convenient Transifex we=
b interface where contributors are able to join by creating a free account.=
 =C2=A0Senior contributors can be promoted to a Reviewer or Maintainer role=
 for each language. =C2=A0Developers pull from Transifex to merge translate=
d strings back into Bitcoin Core.  As a matter of policy translations are N=
OT accepted via Github pull requests as those changes would be overwritten =
by the next Transifex pull and there is no clean way to keep them in sync w=
hen changes are made in both places.</span></p>
<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt"><a href=3D"https://github.com/bitcoin/bitcoin/blob/master/doc/translati=
on_process.md" style=3D"text-decoration:none"><span style=3D"font-size:15px=
;font-family:Arial;text-decoration:underline;vertical-align:baseline;white-=
space:pre-wrap">https://github.com/bitcoin/bitcoin/blob/master/doc/translat=
ion_process.md</span></a></p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"font-size:15px;font-family:Arial;vertical-align:baseline;whi=
te-space:pre-wrap">The latest version of the Translation process can be fou=
nd here.</span></p>
<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt"><span style=3D"font-size:15px;font-family:Arial;font-weight:bold;vertic=
al-align:baseline;white-space:pre-wrap">Bitcoin-Translators Announce-only L=
ist</span></p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<a href=3D"https://groups.google.com/forum/#!forum/bitcoin-translators" sty=
le=3D"text-decoration:none"><span style=3D"font-size:15px;font-family:Arial=
;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">ht=
tps://groups.google.com/forum/#!forum/bitcoin-translators</span></a><span s=
tyle=3D"font-size:15px;font-family:Arial;vertical-align:baseline;white-spac=
e:pre-wrap"><br class=3D"">
Bitcoin-Translators mailing list is an announce-only mailing list for devel=
opers to communicate to translators at particular times when new translatio=
ns are needed. =C2=A0Replies and discussion would go to the bitcoin dev lis=
t. =C2=A0Subscriptions to this list would additionally be valuable to the p=
roject as it allows for a convenient way to ask for translations of other r=
elated projects like <a href=3D"http://bitcoin.org">bitcoin.org</a> that ar=
e hosted on theTransifex platform. =C2=A0Whenever source strings of signifi=
cance are changed or deadlines are announced, translators will learn of wor=
k to be done in Transifex quickly as they will all be subscribed to this an=
nounce list. =C2=A0Discussion of translation issues should be on the Bitcoi=
n-Development list.</span></p>
<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt"><span style=3D"font-size:15px;font-family:Arial;font-weight:bold;vertic=
al-align:baseline;white-space:pre-wrap">Other Improvements to the Translati=
on process</span></p>
<ul style=3D"margin-top:0pt;margin-bottom:0pt"><li dir=3D"ltr" style=3D"lis=
t-style-type:disc;font-size:15px;font-family:Arial;vertical-align:baseline"=
><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"=
><span style=3D"vertical-align:baseline;white-space:pre-wrap">Prior to an i=
ntended release a </span><span style=3D"font-weight:bold;vertical-align:bas=
eline;white-space:pre-wrap">String Freeze</span><span style=3D"vertical-ali=
gn:baseline;white-space:pre-wrap"> is declared on a particular date. =C2=A0=
The string freeze exists to ensure that translators have a reasonable amoun=
t of time to translate new or modified source strings so their work can be =
included in a release.</span></p>
</li><li dir=3D"ltr" style=3D"list-style-type:disc;font-size:15px;font-fami=
ly:Arial;vertical-align:baseline"><p dir=3D"ltr" style=3D"line-height:1.15;=
margin-top:0pt;margin-bottom:0pt"><span style=3D"vertical-align:baseline;wh=
ite-space:pre-wrap">A significant issue with our past translation process w=
as the lack of branch support in Transifex. =C2=A0This meant that since mas=
ter and v0.8.2 diverged in May 2013, translation updates made in Transifex =
were not included in the v0.8.x stable releases until the release of v0.9.0=
 in early 2014. =C2=A0v0.9.1 similarly was released from a branch outside f=
rom master. =C2=A0v0.9.2 is planned to be released directly from the master=
 branch so translations for this upcoming release can be developed directly=
. =C2=A0laanwj came up with a great idea for dealing with future releases w=
here we will be able to keep translations for both diverged stable and mast=
er branch simultaneously in Transifex, with scripts automating the process =
of merging strings and separating them back to the diverged branches.</span=
></p>
</li></ul><div><font face=3D"Arial"><span style=3D"font-size:15px;line-heig=
ht:17.25px;white-space:pre-wrap"><br></span></font></div><div><font face=3D=
"Arial"><span style=3D"font-size:15px;line-height:17.25px;white-space:pre-w=
rap">Please post questions or comments about the release or translation pro=
cess here on Bitcoin-Development list.  Bug reports should be posted a <a h=
ref=3D"https://github.com/bitcoin/bitcoin/issues?direction=3Ddesc&amp;sort=
=3Dupdated&amp;state=3Dopen">Github Issues</a> tickets.</span></font></div>
<div><font face=3D"Arial"><span style=3D"font-size:15px;line-height:17.25px=
;white-space:pre-wrap"><br></span></font></div><div><font face=3D"Arial"><s=
pan style=3D"font-size:15px;line-height:17.25px;white-space:pre-wrap">Warre=
n Togami</span></font></div>
</span></div>

--089e0160b12818451804f7a19d32--