[#30589] [Bug #3391] Use single exclamation mark instead of double exclamation mark for IRB — Diego Viola <redmine@...>

Bug #3391: Use single exclamation mark instead of double exclamation mark for IRB

10 messages 2010/06/04

[#30672] [Bug #3411] Time.local 1916,5,1 #=> 1916-04-30 23:00:00 +0100 — Benoit Daloze <redmine@...>

Bug #3411: Time.local 1916,5,1 #=> 1916-04-30 23:00:00 +0100

12 messages 2010/06/08

[#30699] [Bug #3419] 1.9.2-preview3 possible bug with Rails 3 active_record sqlite_adapter — Joe Sak <redmine@...>

Bug #3419: 1.9.2-preview3 possible bug with Rails 3 active_record sqlite_adapter

9 messages 2010/06/09

[#30734] [Bug #3428] ri outputs ansi escape sequences even when stdout is not a tty — caleb clausen <redmine@...>

Bug #3428: ri outputs ansi escape sequences even when stdout is not a tty

11 messages 2010/06/11

[#30756] [Feature #3436] Spawn the timer thread lazily — Maximilian Gass <redmine@...>

Feature #3436: Spawn the timer thread lazily

15 messages 2010/06/13
[#32686] [Ruby 1.9-Feature#3436] Spawn the timer thread lazily — Mark Somerville <redmine@...> 2010/10/04

Issue #3436 has been updated by Mark Somerville.

[ruby-core:30545] [Ann] Contribution wanted: identify tickets for 1.9.2 release

From: Yusuke ENDOH <mame@...>
Date: 2010-06-01 12:40:52 UTC
List: ruby-core #30545
Hi all --

Toward 1.9.2 release, we will aim to close tickets that holds all of
the following conditions:

  - a ticket is registered in "Ruby 1.9" subproject
  - its "Status" is "open"
  - its "Tracker" is "Bug"
  - its "Priority" is more than "Low"
  - its "Target version" is neither "1.9.x" nor "2.0"

You can see the list:

  http://redmine.ruby-lang.org/projects/ruby-19/issues?query_id=46


Now I'm afraid if some tickets is *lost*.
For example, some may be registered in "Ruby 1.9.1" subproject, even
though it is reproducible in trunk.
But I can't afford to check all tickets of all subproject.

So I want your contribution; if you recognize that any tickets,
especially tickets you registered, seems to be included in the above
list, please check whether or not the issue is still reproducible
with 1.9.2-preview3.  It is better to check with recent ruby_1_9_2
branch, if you can.  And if you could reproduce, please let me know
by adding comment to the ticket or by replying to this thread.  I'll
add the ticket to the above list.

I give you advance notice; we don't promise to fix all tickets you
notify us.  Even if it is actually a bug, we may not fix it unless
it is severe.  This is because we have no enough resource nor time.
But we will make an effort.  I hope you'll understand.

Your contribution would be deeply appreciated.

Thanks,

-- 
Yusuke Endoh <mame@tsg.ne.jp>

In This Thread

Prev Next