[#34011] Should --verbose be equal to -v ? — Yugui <yugui@...>

Yuguiです。

15 messages 2008/03/10
[#34012] Re: Should --verbose be equal to -v ? — Yukihiro Matsumoto <matz@...> 2008/03/10

まつもと ゆきひろです

[#34105] rational.rb, complex.rb and mathn.rb — Tadayoshi Funaba <tadf@...>

rational と complex が組み込みになったことで、lib/mathn.rb の意義は薄

29 messages 2008/03/22
[#34106] Re: rational.rb, complex.rb and mathn.rb — Tadayoshi Funaba <tadf@...> 2008/03/22

現時点で rational.rb と complex.rb を残しているのは、それが無難だから

[#34107] Re: rational.rb, complex.rb and mathn.rb — Tadayoshi Funaba <tadf@...> 2008/03/22

で、かなり選択肢を絞った叩き台です。

[#34120] Re: rational.rb, complex.rb and mathn.rb — keiju@... (石塚圭樹) 2008/03/24

けいじゅ@いしつかです.

[#34125] Re: rational.rb, complex.rb and mathn.rb — Shin-ichiro HARA <sinara@...> 2008/03/25

原です。

[#34130] Re: rational.rb, complex.rb and mathn.rb — Tadayoshi Funaba <tadf@...> 2008/03/25

> 私も Complex の組み込みは Rational とは比較にならないくらい、仕様が決め

[#34158] Complex組み込み — Masahiro TANAKA <masa16.tanaka@...>

Complexが組み込みになるそうですが、これはcomplex.rbを踏襲して、

49 messages 2008/03/27
[#34161] Re: Complex組み込み — Shin-ichiro HARA <sinara@...> 2008/03/28

原です。

[#34168] Re: Complex組み込み — Tadayoshi Funaba <tadf@...> 2008/03/28

> 今までの Complex は、complex.rb にほぼ残して、たとえば Rational 成分

[#34186] Re: Complex組み込み — Shin-ichiro HARA <sinara@...> 2008/03/31

原です。

[#34187] Re: Complex組み込み — Tadayoshi Funaba <tadf@...> 2008/03/31

> そうです。Complex が難しい、という話を書いておくと、

[#34193] Re: Complex組み込み — Yukihiro Matsumoto <matz@...> 2008/03/31

まつもと ゆきひろです

[#34203] Re: Complex組み込み — Tadayoshi Funaba <tadf@...> 2008/04/01

> |僕としては、/ 演算子の振舞いについて前向きに検討してほしいです。

[#34215] Re: Complex組み込み — Yukihiro Matsumoto <matz@...> 2008/04/02

まつもと ゆきひろです

[#34166] Re: Complex組み込み — Tadayoshi Funaba <tadf@...> 2008/03/28

> となるようですが、別の実装として、

[ruby-dev:33949] Re: Schedule for the 1.8.7 release

From: "Akinori MUSHA" <knu@...>
Date: 2008-03-01 12:21:13 UTC
List: ruby-dev #33949
 ということで、 1.8.7 リリースに向けた作業を開始します。

 アナウンスに書いた通り、 1.8.6 からだいぶ間があいたため、これ
までに行われた変更を含めてテストしないといけないこと、 1.9 の
開発がかなり進行し、バックポートや互換性のための変更をこれから
行わねばならないことから、十分に長い準備期間を取る必要があると
判断しました。

 スケジュールに従って、まずは今月22日までにやることのリストを
まとめます。私は3/4〜10の間はおそらくろくに反応できませんが、
それ以外はこまめにチェックします。重要なメールは遠慮なくCcして
ください。

 やることがまとまったら、個々のタスクは Tracker で管理します。

 それでは、よろしくお願いします。

At Sat, 1 Mar 2008 20:58:00 +0900,
I wrote:
> Hi, developers,
>
> After seeing Ruby 1.9.0-1 released earlier today, I, as the release
> manager of the 1.8 series, would like to announce here that it is time
> to start working on the next release, 1.8.7.
>
> Below is the timeline I made up.  The reason for the slow start (long
> period for discussion) is because I'm going on a week's trip next week
> to Portland and Seattle.
>
> Schedule for 1.8.7: (subject to change as it proceeds)
>
>     Now - 2008-03-22
>       Discuss what features should and/or can be backported, and get
>       the release manager to make decisions as to which features are
>       going to be worked on for 1.8.7.
>
>     2008-03-23 18:00:00 JST
>       Declare feature freeze.  The tracker will be keeping a complete
>       list of bugs to fix and new features to implement.
>
>     2008-03-24 - 2008-04-03
>       Work on Tracker issues.  New features must be implemented by the
>       end of this period, while some bugs may remain.
>
>     2008-04-04 12:00:00 JST
>       Declare code freeze.
>
>       - The ruby_1_8_7 branch is forked off from the ruby_1_8 branch.
>
>       - The ruby_1_8_7 branch is frozen from the beginning and any
>         change on the branch requires an explicitly approval by the
>         release manager.
>
>       - The ruby_1_8 branch is not frozen, however, massive changes
>         are forbidden for the moment.
>
>     2008-04-05 18:00:00 JST
>       Release 1.8.7-preview1
>
>     2008-04-12 18:00:00 JST
>       Release 1.8.7-preview2
>
>     2008-04-20 18:00:00 JST
>       Release 1.8.7.
>       Lift code freeze.
>
>
> I realize we have a lot of things to do because the difference between
> 1.9 and 1.8 (1.8.6) has become huge and so many changes have been made
> to 1.8 since 1.8.6 was released.  That is why it is going to take this
> long time to make 1.8.7 a decent release for mission critical scenes
> yet an exciting and beloved release for ambitious users.
>
> Please make sure to Cc me important mails, especially ones that need
> my approval.  I tend to drop a ball on high-volume mailing lists
> because of my poor fast reading skills.
>
> For issue tracking, I made a tracker for 1.8.7 release engineering:
>
>    http://rubyforge.org/tracker/?func=browse&group_id=426&atid=22040
>
> Any changes to the tracker issues will be forwarded to me, so you
> don't have to bother pointing them to me via email.
>
> Now, let's start the work!
>
> Regards,
>
> --
> Akinori MUSHA / http://akinori.org/

--
Akinori MUSHA / http://akinori.org/

In This Thread