[#39222] [Bug #2036] AIX 5L 5.2にて、ruby-1.8.7-p174のビルド時にmake testをするとエラーになった。not ok float 7 -- ./sample/test.rb:1232 — 和弥 寺元 <redmine@...>

Bug #2036: AIX 5L 5.2にて、ruby-1.8.7-p174のビルド時にmake testをするとエラーになった。not ok float 7 -- ./sample/test.rb:1232

13 messages 2009/09/03

[#39249] [Bug #2060] DLをCからRubyに変換する事を勧めます — Aaron Patterson <redmine@...>

Bug #2060: DLをCからRubyに変換する事を勧めます

10 messages 2009/09/07

[#39282] [Bug #2067] bodyが大きいエラーページをopen-uriで取得するとfdがリークしている — takeru sasaki <redmine@...>

チケット #2067 が更新されました。 (by takeru sasaki)

15 messages 2009/09/10
[#39283] Re: [Bug #2067] bodyが大きいエラーページをopen-uriで取得するとfdがリークしている — Yukihiro Matsumoto <matz@...> 2009/09/10

まつもと ゆきひろです

[#39284] Re: [Bug #2067] bodyが大きいエラーページをopen-uriで取得するとfdがリークしている — Nobuyoshi Nakada <nobu@...> 2009/09/10

なかだです。

[#39297] Re: [Bug #2067] bodyが大きいエラーページをopen-uriで取得するとfdがリークしている — Yukihiro Matsumoto <matz@...> 2009/09/10

まつもと ゆきひろです

[#39298] Re: [Bug #2067] bodyが大きいエラーページをopen-uriで取得するとfdがリークしている — Tanaka Akira <akr@...> 2009/09/10

In article <E1MliJq-0000yc-4o@x61.netlab.jp>,

[#39302] Re: [Bug #2067] bodyが大きいエラーページをopen-uriで取得するとfdがリークしている — takeru sasaki <sasaki.takeru@...> 2009/09/10

言いだしっぺの佐々木です。

[#39307] Re: [Bug #2067] bodyが大きいエラーページをopen-uriで取得するとfdがリークしている — Yukihiro Matsumoto <matz@...> 2009/09/10

まつもと ゆきひろです

[#39345] [Bug #2111] Error:test_rm_f(TestFileUtils) — Kazuhiro NISHIYAMA <redmine@...>

Bug #2111: Error:test_rm_f(TestFileUtils)

11 messages 2009/09/17

[#39352] [ruby19] Thread 切替えが異常に遅い? — Hidetoshi NAGAI <nagai@...>

永井@知能.九工大です.

12 messages 2009/09/20

[#39367] Almost endless loop of BigMath::atan(x) when x.abs >= 1 — "Masahiro Kanai (CanI)" <cani.m.61st@...>

金井 仁弘と申します。

13 messages 2009/09/23
[#39980] Re: Almost endless loop of BigMath::atan(x) when x.abs >= 1 — TOYOFUKU Chikanobu <nobu_toyofuku@...> 2010/01/07

豊福です。遅い反応ですが。

[#39982] Re: Almost endless loop of BigMath::atan(x) when x.abs >= 1 — TOYOFUKU Chikanobu <nobu_toyofuku@...> 2010/01/07

豊福です。

[#39388] Re: [ruby-cvs:32331] Ruby:r25113 (trunk): String#inspect's encoding should be fixed. — "Martin J. Dürst" <duerst@...>

成瀬さん、こんにちは。

9 messages 2009/09/28

[ruby-dev:39371] [Proposal] Maintainer confirmation and discharging process

From: Yugui <yugui@...>
Date: 2009-09-25 07:31:53 UTC
List: ruby-dev #39371
2009/9/25 Marc-Andre Lafortune <ruby-core-mailing-list@marc-andre.ca>:
> I hope this, as well as the larger problem of unmaintained / badly
> maintained libraries can be addressed sooner than later:
> http://redmine.ruby-lang.org/wiki/ruby/Unmaintained

Great! thank you.

In addition to the list, some of standard libraries have their
maintainers but the maintainer has not been active.
I hope to make it clear who is the maintainer for each library before
1.9.2's release.
A maintainer has authority to design a library and responsibility for
it. So an inactive maintainer stalls Ruby's development.

I talked with some committers about this topic. As a result, I propose
a maintainer appointment process.

A. Maintainer confirmation process
  If you want to continue to maintain the library, please write your
name onto http://redmine.ruby-lang.org/wiki/ruby/MaintainerConfirmationProcess

B. Maintainer election process
  If a library has no maintainer, anyone can become the maintainer for
it if her/his candidature is accepted in discussion on
ruby-core/ruby-dev.

C. Maintainer discharging process
(1) A maintainer will be discharged when one of the following cases:
     * When (s)he declares her/his resignation as the maintainer.
     * When (s)he has not committed anything for 3 months and (s)he
does not declare that he wants to continue maintenance.
     * When (s)he has not do anything about her/his assigned issues for 3 months
(2) If a maintainer resigns, maintenance of the library will be
temporarily done by the ruby core team until someone become a new
maintainer.
(3) Returning to maintainer after (s)he would be discharged will be welcome.

Thank you.
-- Yugui (Yuki Sonoda)

In This Thread

Prev Next