From: Marc-Andre Lafortune <ruby-core-mailing-list@...>
Date: 2013-02-23T09:53:17+09:00
Subject: [ruby-core:52723] Improving order of NEWS

--047d7bd6bb9ec9867704d659a765
Content-Type: text/plain; charset=ISO-8859-1

I feel the NEWS are in the wrong order: C API, builtin classes, std-lib,
language changes, compatibility.

I realize the C API section is short, but why is it first when 99.9% of
rubyists don't care? Aren't language changes the most important ones, and
if so, why do they come after the std lib?

I would recommend an order based on how many people should know about the
changes:

* Language changes
* Builtin classes
  - Changes
  - Compatibility issues (builtin classes)
* Stdlib
  - Changes
  - Compatibility issues (std-lib)
* C API changes

Objections?

--047d7bd6bb9ec9867704d659a765
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span class=3D"" style=3D"font-family:arial,sans-serif;fon=
t-size:13px"><div><div><div>I feel the NEWS are in the wrong order: C API, =
builtin classes, std-lib, language changes, compatibility.<br></div><div><b=
r></div>

<div>I realize the C API section is short, but why is it first when 99.9% o=
f rubyists don&#39;t care? Aren&#39;t language changes the most important o=
nes, and if so, why do they come after the std lib?</div><div><br></div>

<div>I would recommend an order based on how many people should know about =
the changes:</div><div><br></div><div>* Language changes</div><div>* Builti=
n classes</div><div>=A0 - Changes</div><div>=A0 - Compatibility issues (bui=
ltin classes)</div>

<div>* Stdlib</div><div>=A0 - Changes</div><div>=A0 - Compatibility issues =
(std-lib)</div></div></div><div>* C API changes</div><div><br></div><div>Ob=
jections?</div></span></div>

--047d7bd6bb9ec9867704d659a765--