[#51329] [ruby-trunk - Feature #7677][Open] YAML load mode that does instantiate Ruby — "trans (Thomas Sawyer)" <transfire@...>
7 messages
2013/01/09
[#51347] [ruby-trunk - Bug #7679][Open] IRB history is broken — "zzak (Zachary Scott)" <zachary@...>
15 messages
2013/01/10
[#51348] [ruby-trunk - Bug #7680][Open] IRB autocompletion doesn't autocomplete methods — "zzak (Zachary Scott)" <zachary@...>
8 messages
2013/01/10
[#51389] [ruby-trunk - Bug #7688][Open] Error hiding with rb_rescue() on Comparable#==, #coerce and others — "Eregon (Benoit Daloze)" <redmine@...>
34 messages
2013/01/11
[#59674] [ruby-trunk - Feature #7688] Error hiding with rb_rescue() on Comparable#==, #coerce and others
— "marcandre (Marc-Andre Lafortune)" <ruby-core@...>
2014/01/09
[#59675] [ruby-trunk - Feature #7688] Error hiding with rb_rescue() on Comparable#==, #coerce and others
— "marcandre (Marc-Andre Lafortune)" <ruby-core@...>
2014/01/09
[#59679] Re: [ruby-trunk - Feature #7688] Error hiding with rb_rescue() on Comparable#==, #coerce and others
— "Martin J. Dürst" <duerst@...>
2014/01/10
On 2014/01/10 7:42, marcandre (Marc-Andre Lafortune) wrote:
[#51391] [ANN] Implementer Meeting — Aaron Patterson <tenderlove@...>
Hey everyone,
9 messages
2013/01/11
[#51421] Re: [ANN] Implementer Meeting
— Mark Rada <markrada26@...>
2013/01/14
Hello Aaron,
[#51431] Re: [ANN] Implementer Meeting
— Marc-Andre Lafortune <ruby-core-mailing-list@...>
2013/01/14
I'm worried about issues with Enumerator::Lazy. Should we discuss this at
[#51399] [ruby-trunk - Bug #7689][Open] Crash @enumerator.so with ruby 1.9.3/thin/RoR 3.2.11 — "saepia (Marcin Lewandowski)" <marcin@...>
6 messages
2013/01/12
[#51441] [ruby-trunk - Bug #7699][Open] rubyspec failed: BigDecimal#divmod Can be reversed with * and + — "mrkn (Kenta Murata)" <muraken@...>
8 messages
2013/01/15
[#51453] [REMINDER] Implemeter Meeting — Aaron Patterson <tenderlove@...>
Hey everyone,
5 messages
2013/01/15
[#51454] [CommonRuby - Feature #7701][Open] Non-optional (required) keyword args — "headius (Charles Nutter)" <headius@...>
31 messages
2013/01/15
[#53256] [CommonRuby - Feature #7701] Non-optional (required) keyword args
— "headius (Charles Nutter)" <headius@...>
2013/03/09
[#51496] Ruby 2.0 Meeting Schedule — Aaron Patterson <tenderlove@...>
At the Implemeters Meeting, we talked about meeting again in 2 weeks
5 messages
2013/01/17
[#51497] Schedule next developer meeting — Aaron Patterson <tenderlove@...>
At the last meeting, we agreed upon having another meeting four weeks
5 messages
2013/01/17
[#51499] [ruby-trunk - Feature #7712][Open] Add .txt extensions to all plain-text documentation files for Windows users — "postmodern (Hal Brodigan)" <postmodern.mod3@...>
9 messages
2013/01/18
[#51545] Haiku port problem — Paulo Geyer <paulogeyer@...>
I'm trying to port ruby 1.9.3-p347 to Haiku (http://www.haiku-os.org/)
5 messages
2013/01/21
[#51578] [ruby-trunk - Bug #7729][Open] __dir__ returns a absolute dir path — "authorNari (Narihiro Nakamura)" <authorNari@...>
8 messages
2013/01/23
[#51623] [ruby-trunk - Feature #7739][Open] Define Hash#| as Hash#reverse_merge in Rails — "alexeymuranov (Alexey Muranov)" <redmine@...>
24 messages
2013/01/24
[#51726] [ruby-trunk - Feature #7751][Open] How to encapsulate File.delete and File.rename into one 'transaction'? — "mghomn (Justin Peal)" <yujianbin@...>
5 messages
2013/01/29
[#51735] [ruby-trunk - Bug #7752][Open] Rational/Float/Fixnum/Bignum `.to_s.encoding` is US-ASCII — "coffeejunk (Maximilian Haack)" <mxhaack@...>
6 messages
2013/01/29
[ruby-core:51250] Re: [ruby-dev:46811] Re: [IMPORTANT] 2.0.0 release plan
From:
Yusuke Endoh <mame@...>
Date:
2013-01-05 06:52:50 UTC
List:
ruby-core #51250
ALL COMMITTERS SHOULD READ THIS MAIL! コミッタはこのメール読んで！ ALL COMMITTERS SHOULD READ THIS MAIL! コミッタはこのメール読んで！ ALL COMMITTERS SHOULD READ THIS MAIL! コミッタはこのメール読んで！ Japanese follows; 日本語は後で Sorry for my absence! I tell you about the release plan of 2.0.0. # 2.0.0-rc1 (in a few days) I plan to release 2.0.0-rc1 as soon as there is no "showstopper" issue. Please report to me any showstopper if you know. I consider the following type of issue as a showstopper. * a build failure (in major platforms), * a reproducible segfault (in normal use case), * a problem that significantly affects real/existing programs, or * a serious problem that has no workaround. I'd like to release rc1 tomorrow night in JST if all showstoppers are fixed (or if there is no report). # 2.0.0-rc2 (in early Feb.) You can freely commit any bug fixes (including non-showstopper issues) until 2.0.0-rc2. Note that I plan to prohibit any non-showstopper bug fixes after rc2 (to prevent regression). In other words, you will be able to commit only showstopper fixes after rc2. So, if you have any non-showstopper issue that you want to fix, you must do it in this month. # 2.0.0-p0 (at 24th Feb.) Thanks! しばらく不在にしてすみません。2.0.0 のリリースプランをご連絡します。 # 2.0.0-rc1 (数日以内) "showstopper" な問題がなくなり次第 2.0.0-rc1 をリリースする予定です。 showstopper をご存知であれば申告してください。 以下のような問題を showstopper とみなします。 * (メジャーな環境で) ビルドできない問題 * (通常のユースケースでの) 再現可能な SEGV * 現実の・既存のプログラムに重大な影響を与える問題 * 回避策のない重大な問題 showstopper がすべて修正されたら (または特に申告がなければ) 日本時間の明日の夜に rc1 をリリースしたいと思います。 # 2.0.0-rc2 (2 月上旬) 2.0.0-rc2 までは任意のバグ修正を自由にコミットしてください (showstopper 以外も OK) 。 regression を防ぐため、rc2 以降は showstopper 以外のバグ修正を禁止する予定です。 つまり、rc2 以降は showstopper の修正のみがコミット可能です。 よって、showstopper 以外で修正したい問題があれば、今月中にやってください。 # 2.0.0-p0 (2/24) よろしくお願いします！ 2012/12/27 SASADA Koichi <ko1@atdot.net>: > (English only) > > (I post this message as a substitute of Endo-san, release manager of > Ruby 2.0.0. He is very busy now) > > Thank you for your help. > Now, Ruby 2.0.0 (trunk) is "code freeze" status. > > We want to emphasize the following two things. > > (1) Bug fix only > > Only bug fixes are acceptable before RC2 (beginning of Feb). > > Do *not* add any new features. > If you need to add new features or spec changes to solve an issue, > please get my (Endo-san's) approval. > > > (2) Identify showstoppers > >> ## Identifying showstoppers: ASAP >> >> I will identify "showstoppers" among 300+ bug tickets. They will be >> marked by the immediate priority. A "showstopper" means: >> >> * a reproducible segfault, >> * a problem that significantly affects real/existing programs, or >> * a serious problem that has no workaround. >> >> We will identify bug tickets that are reported after the identifying, >> as needed. > > If you find any *critical* issues as showstoppers, please tell us ASAP. > > > Thank you. > > > (2012/12/03 1:00), Yusuke Endoh wrote: >> ALL COMMITTERS SHOULD READ THIS MAIL! コミッタはこのメール読んで！ >> ALL COMMITTERS SHOULD READ THIS MAIL! コミッタはこのメール読んで！ >> ALL COMMITTERS SHOULD READ THIS MAIL! コミッタはこのメール読んで！ >> >> Japanese follows; 日本語は後で >> >> I tell you the plan for 2.0.0 release. >> Please let me know if you have any idea about the plan, especially, >> if you think that there is a problem in the plan. >> >> ## Milestones >> >> - Identifying showstoppers: ASAP >> - code freeze: 23 Dec. >> - 2.0.0-rc1 release: the first week of Jan. (expected) >> - 2.0.0-rc2 release: the first week of Feb. (expected) >> - 2.0.0-p0 release: 24 Feb. >> >> >> ## Identifying showstoppers: ASAP >> >> I will identify "showstoppers" among 300+ bug tickets. They will be >> marked by the immediate priority. A "showstopper" means: >> >> * a reproducible segfault, >> * a problem that significantly affects real/existing programs, or >> * a serious problem that has no workaround. >> >> We will identify bug tickets that are reported after the identifying, >> as needed. >> >> >> ## Code freeze: 23 Dec. >> >> Or, feature implementation deadline. 2.0.0 will NOT include the >> (even accepted) new features that are not implemented by this >> deadline. >> >> >> ## 2.0.0-rc1 release: the first week of Jan. (expected) >> >> After all showstoppers are resolved, we will release 2.0.0-rc1. >> (It may be late depending on the status.) >> >> I'll determine "platform support level" based on whether rc1 works >> properly on the platform or not. >> After 2.0.0-rc1, we will try to resolve non-showstopper bug tickets >> as many as possible. >> >> >> ## 2.0.0-rc2 release: the first week of Feb. (expected) >> >> After we resolve showstoppers that are reported after rc1, we >> will release 2.0.0-rc2. >> >> I'd like to create a new branch ruby_2_0 at this time. >> >> After 2.0.0-rc2, we will try to resolve only showstoppers reported >> after rc2. In principle, we will NOT resolve non-showstoppers to >> avoid a regression. >> >> >> ## 2.0.0-p0 release: 24 Feb. >> >> PARTY! >> >> >> >> 2.0.0 リリースの予定をお伝えします。 >> この予定に関して何か意見があれば (特に問題があると思う場合は) ぜひ >> 教えてください。 >> >> ## イベント >> >> - showstopper の同定: なるべく早めに >> - コードフリーズ: 12/23 >> - 2.0.0-rc1 リリース: 1 月第一週目標 >> - 2.0.0-rc2 リリース: 2 月第一週目標 >> - 2.0.0-p0 リリース: 2/24 >> >> >> ## showstopper の同定: なるべく早めに >> >> 300 件あまりあるバグチケットから showstopper を同定します (優先度を >> Immediate にします) 。showstopper とは以下を指します。 >> >> * 再現性のある SEGV >> * 実世界の、または既存のプログラムに重大な影響を与える問題 >> * 回避策がない重大な問題 >> >> その後報告されたバグチケットは随時判断します。 >> >> >> ## コードフリーズ: 12/23 >> >> 新機能実装締め切りです。この締め切りまでに実装されなかった新機能は >> (たとえ accept されているものでも) 2.0.0 に含まれません。 >> >> >> ## 2.0.0-rc1 リリース: 1 月第一週目標 >> >> すべての showstopper が解消されたら、2.0.0-rc1 を出します。 >> (進捗次第で遅れるかもしれません) >> >> rc1 の動作実績を元に platform support level を決めようと思います。 >> 2.0.0-rc1 の後は、showstopper でないバグチケットを出来るだけ解決 >> するよう努力します。 >> >> >> ## 2.0.0-rc2 リリース: 2 月第一週目標 >> >> rc1 の後で報告された showstopper を解決した後で、2.0.0-rc2 を >> リリースします。 >> >> この時に ruby_2_0 のブランチを作りたいと思います。 >> >> 2.0.0-rc2 の後では、rc2 後に報告された showstopper のみ解決します。 >> regression を避けるため、原則として、showstopper でない問題の修正は >> 行いません。 >> >> >> ## 2.0.0-p0 release: 2/24 >> >> パーティー！ >> > > > -- > // SASADA Koichi at atdot dot net > -- Yusuke Endoh <mame@tsg.ne.jp>