[#54738] [ruby-trunk - Bug #8358][Open] TestSprintf#test_float test failuer on mingw32 — "phasis68 (Heesob Park)" <phasis@...>

36 messages 2013/05/02

[#54749] [ruby-trunk - Feature #8361][Open] Alternative syntax for block parameter — "alexeymuranov (Alexey Muranov)" <redmine@...>

12 messages 2013/05/02

[#54798] [ruby-trunk - Bug #8370][Open] Constants MAX_MULTIPART_LENGTH in cgi\core.rb — "xibbar (Takeyuki FUJIOKA)" <xibbar@...>

17 messages 2013/05/05

[#54850] [ruby-trunk - Feature #8377][Open] Deprecate :: for method calls in 2.1 — "charliesome (Charlie Somerville)" <charliesome@...>

27 messages 2013/05/07

[#54881] [ruby-trunk - Bug #8384][Open] Cannot build ruby against OpenSSL build with "no-ec2m" — "vo.x (Vit Ondruch)" <v.ondruch@...>

16 messages 2013/05/09

[#54921] [ruby-trunk - Bug #8393][Open] A class who's parent class is in a module can go wrong if files are required in the wrong order — "eLobato (Daniel Lobato Garcia)" <elobatocs@...>

15 messages 2013/05/12

[#54939] [ruby-trunk - Bug #8399][Open] Remove usage of RARRAY_PTR in C extensions when not needed — "dbussink (Dirkjan Bussink)" <d.bussink@...>

32 messages 2013/05/12

[#55053] [ruby-trunk - Feature #8426][Open] Implement class hierarchy method caching — "charliesome (Charlie Somerville)" <charliesome@...>

21 messages 2013/05/19

[#55096] [ruby-trunk - Feature #8430][Open] Rational number literal — "mrkn (Kenta Murata)" <muraken@...>

28 messages 2013/05/21

[#55197] [ruby-trunk - Feature #8461][Open] Easy way to disable certificate checking in XMLRPC::Client — "herwinw (Herwin Weststrate)" <herwin@...>

11 messages 2013/05/29

[ruby-core:54903] Re: Plan to the first 2.0.0 patchlevel release.

From: Tomoyuki Chikanaga <nagachika00@...>
Date: 2013-05-10 15:45:11 UTC
List: ruby-core #54903
Hello,


> I don't understand your comment.
>
> Is your concern that the internal improvement patches are too complex to backport this close to the
> coming release, but you plan to backport them for the next 2.0.0 patchlevel release?
No.
Basically, optimization is not a subject of backport.
If you think they are worth enough to backport, please move the
tickets to Ruby200 project,
or file a backport ticket with your reason.


2013/5/6 Jon <jon.forums@gmail.com>:
>> > #8142
>> > #8143
>> > #8149
>> These seem like performance optimization patches.
>> The optimization patches have less priority for backport.
>> I think a patch achieves noticeable performance improvement could be treated
>> as "a bug fix". It'll fixes a heavy performance reduction ;-)
>> But now, just before the coming release, I want to be conservative.
>
> I don't understand your comment.
>
> Is your concern that the internal improvement patches are too complex to backport this close to the
> coming release, but you plan to backport them for the next 2.0.0 patchlevel release?
>
> Jon
>

In This Thread