[#40528] [Feature #2833] 絵文字エンコーディングの提案 — Kenta Murata <redmine@...>

Feature #2833: 絵文字エンコーディングの提案

32 messages 2010/03/02
[#40530] Re: [Feature #2833] 絵文字エンコーディングの提案 — Yukihiro Matsumoto <matz@...> 2010/03/02

まつもと ゆきひろです

[#40597] Re: [ruby-list:46898] 重複組合せは組込みにならないのでしょうか? — "KISHIMOTO, Makoto" <[email protected]>

きしもとです

17 messages 2010/03/12
[#40598] Re: [ruby-list:46898] 重複組合せは組込みにならないのでしょうか? — Yukihiro Matsumoto <matz@...> 2010/03/12

まつもと ゆきひろです

[#40601] Re: [ruby-list:46898] 重複組合せは組込みにならないのでしょうか? — Yusuke ENDOH <mame@...> 2010/03/12

遠藤です。

[#40608] Re: 組込みの重複順列・重複組合せ — "KISHIMOTO, Makoto" <[email protected]> 2010/03/13

> 同様に、repeated_permutation/combination のデフォルト引数にも反対

[#40610] Re: 組込みの重複順列・重複組合せ — Yukihiro Matsumoto <matz@...> 2010/03/13

まつもと ゆきひろです

[#40641] [Bug #2965] method `===' called on hidden T_STRING object (NotImplementedError) — Kenta Murata <redmine@...>

Bug #2965: method `===' called on hidden T_STRING object (NotImplementedError)

12 messages 2010/03/15

[#40649] [Feature #2968] 数値の正負を返すメソッド — Yui NARUSE <redmine@...>

Feature #2968: 数値の正負を返すメソッド

17 messages 2010/03/15

[#40650] [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — Yui NARUSE <redmine@...>

Feature #2969: String#to_f が -h.hhh±pd を解釈できるように

38 messages 2010/03/15
[#40728] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — Tadayoshi Funaba <tadf@...> 2010/03/22

質問ですが、この形式は入力だけでなく、なんらかの方法で出力でも利用でき

[#40732] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — "NARUSE, Yui" <naruse@...> 2010/03/22

成瀬です。

[#40736] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — Tadayoshi Funaba <tadf@...> 2010/03/23

> String#to_f は従来から指数表記を許していたので、

[#40738] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — "NARUSE, Yui" <naruse@...> 2010/03/23

成瀬です。

[#40745] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — Tadayoshi Funaba <tadf@...> 2010/03/24

> to_i がデフォルトで prefix を見ないのは、0377 のような、

[#40747] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — "NARUSE, Yui" <naruse@...> 2010/03/24

成瀬です。

[#40749] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — Tadayoshi Funaba <tadf@...> 2010/03/24

> 先のパッチの対象関数が ruby_strtod である通り、

[#40759] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — "NARUSE, Yui" <naruse@...> 2010/03/25

成瀬です。

[#40762] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — Tadayoshi Funaba <tadf@...> 2010/03/25

> strtod(3) の解釈対象に含まれていない 2 進や 8 進を否定することが、

[#40763] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — "NARUSE, Yui" <naruse@...> 2010/03/25

(2010/03/26 3:05), Tadayoshi Funaba wrote:

[#40764] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — Tadayoshi Funaba <tadf@...> 2010/03/25

> なぜ同じなのでしょう。

[#40782] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — "NARUSE, Yui" <naruse@...> 2010/03/26

(2010/03/26 4:02), Tadayoshi Funaba wrote:

[#40786] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — KOSAKI Motohiro <kosaki.motohiro@...> 2010/03/27

>> strtod(3) を参考にしたり、影響されたりすることは普通にあるとは思います

[#40788] Re: [Feature #2969] String#to_f が -h.hhh±pd を解釈できるように — "NARUSE, Yui" <naruse@...> 2010/03/27

(2010/03/27 18:19), KOSAKI Motohiro wrote:

[#40695] keiju, please check tickets assigned to you — Yusuke ENDOH <mame@...>

いしつかさん

15 messages 2010/03/18

[#40779] [Feature #3018] UNINITIALIZED_VAR() マクロの導入 — Motohiro KOSAKI <redmine@...>

Feature #3018: UNINITIALIZED_VAR() マクロの導入

12 messages 2010/03/26

[#40805] Improvement of Fiber switching cost with system dependent way — SASADA Koichi <ko1@...>

 ささだです.

10 messages 2010/03/28

[ruby-dev:40648] [ANN] 1.9.2 release plan

From: Yusuke ENDOH <mame@...>
Date: 2010-03-15 14:11:41 UTC
List: ruby-dev #40648
Hi,

We announce 1.9.2 release plan:

  - 31 Mar.  freeze the spec
  - 30 Apr.  freeze the code
  - 31 May.  release 1.9.2-preview2
  - 30 Jun.  release 1.9.2-rc
  - 31 Jul.  release 1.9.2-p0

The following will be proceeded at each event:


=== freeze the spec (31 Mar.) ===

* close and identify 1.9.2 feature tickets

  - 1.9.2 will NOT include all features that we cannot agree by this
    time; target of the ticket will be changed to 1.9.x
  - 1.9.2 will NOT include all features suggested after this time

  - exception: The spec detail of "DL powered by libffi" feature can
    be changed until 30 Apr., because we consider that the feature is
    important for inter-implementation compatibility.  But we will
    not allow after April.  Aaron, keep up your good work!


=== freeze the code (30 Apr.) ===

* close feature implementation for 1.9.2

  - 1.9.2 will NOT include all features that are not implemented and
    committed by this time (even if the ticket is agreed at 31 Mar.)
  - (inadvisable hint: feature request will survive as long as any
     change to aim to implement the feature is committed, even if the
     change is buggy a little)

* create ruby_1_9_2 branch

  - do NOT commit anything that breaks the frozen feature to trunk
    until this time


=== release 1.9.2-preview2 (31 May.) ===

* fix 1.9.2 feature set

  - 1.9.2 will NOT include all features that are not stable yet or that
    are considered uncompleted at this time; they will be reverted

* identify bug tickets that should be fixed in 1.9.2

  - bug tickets registered after this time will be consider; but they
    will be evaluated more conservatively (e.g., bug report based on
    just "reporter's intuition" will be rejected or deferred to 1.9.x)

* call for 3rd party to check 1.9.2-preview2

  - please check the release on various platforms
  - please check and fix "1.9-ready" projects on the release

This release may be delayed (at most) a week only if some "essential"
feature (e.g., dl on libffi) are not stable yet.


=== release 1.9.2-rc (30 Jun.) ===

* finish to fix 1.9.2 bug tickets

  - if we figure out that an issue needs major change of 1.9.2, and if
    the issue is not vital, it will be deferred to 1.9.x.

This release may be delayed as long as any bug tickets remain.


=== release 1.9.2-p0 (31 Jul.) ===

* wait for bug report in about two weeks

After that, when there is no bug ticket, 1.9.2-p0 will be released.


This plan is approved by Yugui, the 1.9 release manager.
At first, you should hurry to appeal your feature request, if any.

Thanks,

-- 
Yusuke ENDOH <[email protected]>

In This Thread

Prev Next