[#67346] Future of test suites for Ruby — Charles Oliver Nutter <headius@...>
I'll try to be brief so we can discuss all this. tl;dr: RubySpec is
19 messages
2015/01/05
[#67353] Re: Future of test suites for Ruby
— Tanaka Akira <akr@...>
2015/01/05
2015-01-06 7:18 GMT+09:00 Charles Oliver Nutter <headius@headius.com>:
[#67444] [ruby-trunk - Feature #10718] [Open] IO#close should not raise IOError on closed IO objects. — akr@...
Issue #10718 has been reported by Akira Tanaka.
3 messages
2015/01/09
[#67689] Keyword Arguments — Anthony Crumley <anthony.crumley@...>
Please forgive my ignorance as I am new to MRI development and am still
5 messages
2015/01/20
[#67733] [ruby-trunk - Bug #10761] Marshal.dump 100% slower in 2.2.0 vs 2.1.5 — normalperson@...
Issue #10761 has been updated by Eric Wong.
4 messages
2015/01/21
[#67736] Re: [ruby-trunk - Bug #10761] Marshal.dump 100% slower in 2.2.0 vs 2.1.5
— Eric Wong <normalperson@...>
2015/01/22
normalperson@yhbt.net wrote:
[#67772] Preventing Redundant Email Messages — Jeremy Evans <code@...>
For a long time, I've wondered why I sometimes receive redundant email
5 messages
2015/01/23
[ruby-core:67701] [ruby-trunk - Bug #10760] [Open] NEWS file should include ticket / reference
From:
e@...
Date:
2015-01-20 18:50:54 UTC
List:
ruby-core #67701
Issue #10760 has been reported by Zachary Scott. ---------------------------------------- Bug #10760: NEWS file should include ticket / reference https://bugs.ruby-lang.org/issues/10760 * Author: Zachary Scott * Status: Open * Priority: Normal * Assignee: * ruby -v: 2.3.0 * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- Currently our [NEWS](https://github.com/ruby/ruby/blob/trunk/NEWS) file doesn't include any reference to the change, just a brief description. I think we should follow similar conventions to Rails [release notes](https://github.com/rails/rails/blob/master/guides/source/4_2_release_notes.md) and include this reference. It doesn't have to be a link, just a simple [Feature #8888] and will help users who are upgrading to easier find the background of these changes. I don't suggest retroactive for existing releases, but for current development (2.3.0) we should make this a priority. -- https://bugs.ruby-lang.org/