[#29270] Proposal: Module#thunk_method — Charles Oliver Nutter <headius@...>

Many people use define_method solely so they can define a new method

13 messages 2010/04/06

[#29293] URI.(un)escape deprecated? — Marc-Andre Lafortune <ruby-core-mailing-list@...>

Hi.

16 messages 2010/04/07
[#29366] Re: URI.(un)escape deprecated? — Tanaka Akira <akr@...> 2010/04/08

2010/4/7 Marc-Andre Lafortune <ruby-core-mailing-list@marc-andre.ca>:

[#29313] [Bug #3112] require "yaml" doesn't use psych as default — Usaku NAKAMURA <redmine@...>

Bug #3112: require "yaml" doesn't use psych as default

28 messages 2010/04/08
[#29315] [Bug #3112] require "yaml" doesn't use psych as default — Yui NARUSE <redmine@...> 2010/04/08

Issue #3112 has been updated by Yui NARUSE.

[#29336] Re: [Bug #3112] require "yaml" doesn't use psych as default — Aaron Patterson <aaron@...> 2010/04/08

On Thu, Apr 08, 2010 at 02:06:55PM +0900, Yui NARUSE wrote:

[#29395] [Bug #3119] [Patch] "IOError (closed stream)" error with tempfile unlink then close usage — Simon Nicholls <redmine@...>

Bug #3119: [Patch] "IOError (closed stream)" error with tempfile unlink then close usage

9 messages 2010/04/09

[#29427] [Bug #3124] SocketError on SnowLeopard (during make test-all) — Aaron Patterson <redmine@...>

Bug #3124: SocketError on SnowLeopard (during make test-all)

10 messages 2010/04/11

[#29462] [Feature #3131] add Kernel#Hash() method like Kernel#Array() — Suraj Kurapati <redmine@...>

Feature #3131: add Kernel#Hash() method like Kernel#Array()

10 messages 2010/04/11

[#29464] [Bug #3132] …/nokogiri-1.4.1/ext/nokogiri/nokogiri.bundle: [BUG] Bus Error — Ashley Williams <redmine@...>

Bug #3132: …/nokogiri-1.4.1/ext/nokogiri/nokogiri.bundle: [BUG] Bus Error

8 messages 2010/04/12

[#29486] [Bug #3140] gem activation has changed between 1.8 and 1.9 — Aaron Patterson <redmine@...>

Bug #3140: gem activation has changed between 1.8 and 1.9

102 messages 2010/04/13
[#31002] [Bug #3140] gem activation has changed between 1.8 and 1.9 — Aaron Patterson <redmine@...> 2010/07/02

Issue #3140 has been updated by Aaron Patterson.

[#31003] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yusuke ENDOH <mame@...> 2010/07/02

Hi,

[#31005] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yehuda Katz <wycats@...> 2010/07/02

We are about to ship a version of Ruby with a built in package manager with

[#29489] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Evan Phoenix <evan@...> 2010/04/13

After a brief discussion with Eric Hodel about this, there are a few questions before we can figure out how to solve this:

[#29513] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Evan Phoenix <evan@...> 2010/04/14

Is there any comment on this? This is a big bug in 1.9.2 that we'd like to get fixed as soon as we can, but I need some input on it.

[#29526] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Rich Kilmer <rich.kilmer@...> 2010/04/15

I wrote this original code in gem_prelude.

[#31104] [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yusuke Endoh <redmine@...> 2010/07/07

Issue #3140 has been updated by Yusuke Endoh.

[#31108] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Roger Pack <rogerdpack2@...> 2010/07/07

> I've commited the patch to trunk.

[#31193] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yusuke ENDOH <mame@...> 2010/07/11

Hi,

[#31223] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Roger Pack <rogerdpack2@...> 2010/07/12

> Roger, could you re-try to build from scratch? ould you apply

[#31215] [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yehuda Katz <redmine@...> 2010/07/12

Issue #3140 has been updated by Yehuda Katz.

[#31218] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yukihiro Matsumoto <matz@...> 2010/07/12

Hi,

[#29528] [Bug #3150] net/https peer verification doesn't do anything — Hongli Lai <redmine@...>

Bug #3150: net/https peer verification doesn't do anything

11 messages 2010/04/15

[#29578] [Bug #3163] SyntaxError when using variable which is also a method in current scope with a Symbol argument — Benoit Daloze <redmine@...>

Bug #3163: SyntaxError when using variable which is also a method in current scope with a Symbol argument

17 messages 2010/04/17
[#29583] [Bug #3163] SyntaxError when using variable which is also a method in current scope with a Symbol argument — caleb clausen <redmine@...> 2010/04/18

Issue #3163 has been updated by caleb clausen.

[#29641] [Feature #3176] Thread#priority= should actually do something — caleb clausen <redmine@...>

Feature #3176: Thread#priority= should actually do something

28 messages 2010/04/19

[#29710] [Bug #3185] File.expand_path repeats forward slashes at the beginning of the path — Brian Ford <redmine@...>

Bug #3185: File.expand_path repeats forward slashes at the beginning of the path

10 messages 2010/04/21

[#29835] [Bug #3212] ConditionVariable may become inconsistent for interrupted threads — Sylvain Joyeux <redmine@...>

Bug #3212: ConditionVariable may become inconsistent for interrupted threads

24 messages 2010/04/28

[#29868] [Bug:trunk] assert now passes non-boolean result — Nobuyoshi Nakada <nobu@...>

Hi,

15 messages 2010/04/29

[ruby-core:29882] Plan to Support Levels for Ruby 1.9.2

From: Yugui <yugui@...>
Date: 2010-04-29 13:39:13 UTC
List: ruby-core #29882
HI,

Before release of Ruby 1.9.2, I would like to define a new guideline
of the support levels for Ruby 1.9.2.

== Definition of the support levels
The Ruby 1.9 series have four support levels.

(1) Supported:
  We ensure Ruby works fine before release. I do not release Ruby when
an issue (†1) remains on a supported platform.

  A platform can be "supported" when:
  * Ruby is maintained on it (†2),
  * And Ruby passes almost all the test cases and RubySpec on it,
  * And we have a continuous build environment for Ruby on it,
  * And it have been "supported" or "best effort" for more than an year.

(2) Best effort:
  We are trying making Ruby to work fine on it.
  I do not release Ruby when an serious issue remains on a best effort platform.

  A platform can be "best effort" when:
  * Ruby is maintained on it,
  * And Ruby passes most of the test cases and RubySpec on it

(3) Perhaps:
  We think Ruby works on it, however, we do not care about it.
  I sometimes release Ruby even if there are issues on it.

  A platform can be "perhaps" when:
  * A similar platform is "supported" or "best effort",
  * Or Ruby is maintained on it
  * Or a patch is recently applied for Ruby on the platform, and it is
reported that Ruby works fine on it because of the patch.

(4) Not supported:
  We do not think Ruby works on it. A patch is always welcome.
  * Any other systems


†1:
  A "Issue" means one on the redmine (http://redmine.ruby-lang.org )
†2:
  Ruby is "maintained" on a platform when:
  * At least one committer always develops Ruby on the platform
  * Or there is an assigned maintainer of Ruby for it

== List of candidate platforms
Candidate for the "supported" platforms of Ruby 1.9.2 is only
  * Debian GNU/Linux stable version on i386
  however the following two platforms can be the candidates if a
continuous build environment is available:
  * Mac OS X 10.5, 10.6 on Intel
  * FreeBSD 6 or later (amd64, IA32)

Candidates for the "best effort platforms" are:
  * Mac OS X 10.5, 10.6 on Intel
  * FreeBSD 6 or later (amd64, IA32)
  * Solaris 10 / OpenSolaris
  * mswin32, mswin64, mingw32
  * AIX 5.3 on PowerPC

AIX will be possibly "perhaps". It depends on progress of development.

Candidates for the "perhaps" platforms are:
  * Other versions of Debian GNU/Linux.
    * or stable version on other architectures
  * Other Linux distributions
  * Mac OS X 10.5 on PPC
  * cygwin
  * Other POSIX-compatible systems
  * BeOS (Haiku)

Another platform can be a candidate for "best effort" or "perhaps".
You can add your platform to the list by satisfying the following
definition.
Let us know if you have a continuous build environment.

== Schedule
2010-06-15:
  The list of candidates will be fixed.
2010-06-30:
  The supported platforms and the support levels will be fixed.


Thank you,
-- Yuki Sonoda (Yugui)

In This Thread

Prev Next