[#53944] [ruby-trunk - Bug #8210][Open] Multibyte character interfering with end-line character within a regex — "sawa (Tsuyoshi Sawada)" <sawadatsuyoshi@...>

14 messages 2013/04/03

[#53974] [ruby-trunk - Feature #8215][Open] Support accessing Fiber-locals and backtraces for a Fiber — "halorgium (Tim Carey-Smith)" <ruby-lang-bugs@...>

14 messages 2013/04/03

[#54095] [ruby-trunk - Feature #8237][Open] Logical method chaining via inferred receiver — "wardrop (Tom Wardrop)" <tom@...>

34 messages 2013/04/08

[#54138] [ruby-trunk - Bug #8241][Open] If uri host-part has underscore ( '_' ), 'URI#parse' raise 'URI::InvalidURIError' — "neocoin (Sangmin Ryu)" <neocoin@...>

9 messages 2013/04/09

[#54185] [CommonRuby - Feature #8257][Open] Exception#cause to carry originating exception along with new one — "headius (Charles Nutter)" <headius@...>

43 messages 2013/04/11

[#54196] Encouraging use of CommonRuby — Charles Oliver Nutter <headius@...>

I think we need to do more to encourage the use of the CommonRuby

20 messages 2013/04/11
[#54200] Re: Encouraging use of CommonRuby — Marc-Andre Lafortune <ruby-core-mailing-list@...> 2013/04/11

Hi,

[#54211] Re: Encouraging use of CommonRuby — "NARUSE, Yui" <naruse@...> 2013/04/12

As far as I understand, what is CommonRuby and the process over CommonRuby

[#54207] [CommonRuby - Feature #8258][Open] Dir#escape_glob — "steveklabnik (Steve Klabnik)" <steve@...>

15 messages 2013/04/12

[#54218] [CommonRuby - Feature #8259][Open] Atomic attributes accessors — "funny_falcon (Yura Sokolov)" <funny.falcon@...>

43 messages 2013/04/12

[#54288] [CommonRuby - Feature #8271][Open] Proposal for moving to a more visible, formal process for feature requests — "headius (Charles Nutter)" <headius@...>

15 messages 2013/04/15

[#54333] Requesting Commit Access — Aman Gupta <ruby@...1.net>

Hello ruby-core,

16 messages 2013/04/16

[#54473] [Backport 200 - Backport #8299][Open] Minor error in float parsing — "bobjalex (Bob Alexander)" <bobjalex@...>

27 messages 2013/04/19

[#54532] [ruby-trunk - Bug #8315][Open] mkmf does not include include paths from pkg_config anymore — "Hanmac (Hans Mackowiak)" <hanmac@...>

11 messages 2013/04/23

[#54621] [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI — "ko1 (Koichi Sasada)" <redmine@...>

43 messages 2013/04/27
[#54643] [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI — "authorNari (Narihiro Nakamura)" <authorNari@...> 2013/04/28

[#54649] Re: [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby/MRI — SASADA Koichi <ko1@...> 2013/04/28

(2013/04/28 9:23), authorNari (Narihiro Nakamura) wrote:

[#54657] Re: [ruby-trunk - Feature #8339][Open] Introducing Geneartional Garbage Collection for CRuby/MRI — Magnus Holm <judofyr@...> 2013/04/28

On Sat, Apr 27, 2013 at 8:19 PM, ko1 (Koichi Sasada)

[#54665] [ruby-trunk - Bug #8344][Open] Status of Psych and Syck — "Eregon (Benoit Daloze)" <redmine@...>

18 messages 2013/04/28

[ruby-core:54228] Re: Encouraging use of CommonRuby

From: Rodrigo Rosenfeld Rosas <rr.rosas@...>
Date: 2013-04-12 15:07:44 UTC
List: ruby-core #54228
Em 12-04-2013 10:59, NARUSE, Yui escreveu:
> (2013/04/12 22:09), Rodrigo Rosenfeld Rosas wrote:
>> But if otherwise you're interested in discussing such changes before t=
hey get approved by Matz but doesn't want to have to read all other MRI s=
pecifics tickets, then I feel your pain. Unfortunately I believe Redmine =
(nor even latest versions) support tagging tickets. If it allowed tagging=
 them it would be just a matter of tagging such common tickets like "comm=
on" and "approved" and provide some news feeds interface so that you coul=
d look at them separately, although I still believe it would be hard anyw=
ay to get a quick overview of those tickets as they usually contain a lot=
 of comments. So maybe it would be good if we could tag some tickets as "=
common Ruby" and whenever a ticket containing lots of comments get approv=
ed, maybe we should close that ticket, create a new one with the summary =
of what should be changed and reference the old ticket in case someone wa=
nts to look at the full log.
>>
>> Just to let you know, Redmine maintainers are favorable to introducing=
 issues tagging to Redmine:
>>
>> http://www.redmine.org/issues/1448
>>
>> So, if you believe that would help, maybe we could try to get this imp=
lemented in Redmine and start using the newest version...
> I hadn't know the issue, but custom fields can be usable for this usage=
 as I wrote in [ruby-core:54220].

Great idea, indeed.

>> Anyway, this is just an idea. I'm sorry since I said I would help upda=
ting Redmine but since my daughter is about to born any time now I can't =
find much free time to focus on this upgrade, although it shouldn't be th=
at hard. I already tested that it is possible to simply run the newest mi=
grations to the current database and run the newest Redmine on it. It is =
just a matter now to test the mailing list integration plugin into this n=
ew Redmine and fix any incompatibilities that may have appeared in the AP=
I since it was first implemented. I'm not sure yet how I can test this ma=
iling list integration plugin but I didn't start to try yet so maybe when=
 I start I'll create tickets in the project asking for help.
> For people don't not it yet, following is the issue.
> https://github.com/asakusarb/redmine4ruby-lang/issues/21

Thanks, I wasn't aware of that yet... :)


In This Thread