[#15707] Schedule for the 1.8.7 release — "Akinori MUSHA" <knu@...>

Hi, developers,

21 messages 2008/03/01

[#15740] Copy-on-write friendly garbage collector — Hongli Lai <hongli@...99.net>

Hi.

31 messages 2008/03/03
[#15742] Re: Copy-on-write friendly garbage collector — Yukihiro Matsumoto <matz@...> 2008/03/03

Hi,

[#15829] Re: Copy-on-write friendly garbage collector — Daniel DeLorme <dan-ml@...42.com> 2008/03/08

Yukihiro Matsumoto wrote:

[#15756] embedding Ruby 1.9.0 inside pthread — "Suraj Kurapati" <sunaku@...>

Hello,

18 messages 2008/03/03
[#15759] Re: embedding Ruby 1.9.0 inside pthread — Nobuyoshi Nakada <nobu@...> 2008/03/04

Hi,

[#15760] Re: embedding Ruby 1.9.0 inside pthread — Yukihiro Matsumoto <matz@...> 2008/03/04

Hi,

[#15762] Re: embedding Ruby 1.9.0 inside pthread — "Suraj N. Kurapati" <sunaku@...> 2008/03/04

Yukihiro Matsumoto wrote:

[#15783] Adding startup and shutdown to Test::Unit — Daniel Berger <Daniel.Berger@...>

Hi all,

15 messages 2008/03/04

[#15835] TimeoutError in core, timeouts for ConditionVariable#wait — MenTaLguY <mental@...>

I've been reworking JRuby's stdlib to improve performance and fix

10 messages 2008/03/09

[#15990] Recent changes in Range#step behavior — "Vladimir Sizikov" <vsizikov@...>

Hi,

35 messages 2008/03/23
[#15991] Re: Recent changes in Range#step behavior — Dave Thomas <dave@...> 2008/03/23

[#15993] Re: Recent changes in Range#step behavior — "Vladimir Sizikov" <vsizikov@...> 2008/03/23

Hi Dave,

[#15997] Re: Recent changes in Range#step behavior — Dave Thomas <dave@...> 2008/03/23

[#16024] Re: Recent changes in Range#step behavior — "Vladimir Sizikov" <vsizikov@...> 2008/03/26

Hi Dave,

[#16025] Re: Recent changes in Range#step behavior — Yukihiro Matsumoto <matz@...> 2008/03/26

Hi,

[#16026] Re: Recent changes in Range#step behavior — Dave Thomas <dave@...> 2008/03/26

[#16027] Re: Recent changes in Range#step behavior — Yukihiro Matsumoto <matz@...> 2008/03/26

Hi,

[#16029] Re: Recent changes in Range#step behavior — Dave Thomas <dave@...> 2008/03/26

[#16030] Re: Recent changes in Range#step behavior — Yukihiro Matsumoto <matz@...> 2008/03/26

Hi,

[#16031] Re: Recent changes in Range#step behavior — Dave Thomas <dave@...> 2008/03/26

[#16032] Re: Recent changes in Range#step behavior — "Vladimir Sizikov" <vsizikov@...> 2008/03/26

On Wed, Mar 26, 2008 at 7:01 PM, Dave Thomas <dave@pragprog.com> wrote:

[#16033] Re: Recent changes in Range#step behavior — Dave Thomas <dave@...> 2008/03/26

[#16041] Re: Recent changes in Range#step behavior — David Flanagan <david@...> 2008/03/26

Dave Thomas wrote:

Re: Test::Unit maintainer

From: Kouhei Sutou <kou@...>
Date: 2008-03-22 00:43:18 UTC
List: ruby-core #15979
Hi,

In <1F08809E-7875-462E-AB81-11BA07D6048D@zenspider.com>
  "Re: Test::Unit maintainer" on Sat, 22 Mar 2008 09:04:24 +0900,
  Ryan Davis <ryand-ruby@zenspider.com> wrote:

> 
> On Mar 21, 2008, at 16:54 , Kouhei Sutou wrote:
> 
> > Which way should I use to develop test/unit?
> >
> >  1. Use the Ruby repository's trunk as the test/unit main
> >     repository. The test/unit repository on RubyForge is
> >     used just for preview release. (Official release is
> >     ruby release.)
> >
> >     1-1. develop some features on the Ruby repository's trunk.
> >     1-2. merge changes on the Ruby repository's trunk to
> >          the test/unit repository's trunk on RubyForge.
> >     1-3. release a new version as a gem on RubyForge.
> >     1-4. back to 1-1.
> >
> >  2. Use the test/unit repository on RubyForge as the test/unit
> >     main repository. Developed features are merged to the
> >     Ruby repository's trunk after preview release on RubyForge.
> >
> >     2-1. develop some features on the test/unit
> >          repository's trunk on RubyForge.
> >     2-2. release a new version as a gem on RubyForge.
> >     2-3. merge changes on the test/unit repository's trunk
> >          on RubyForge to the Ruby repository's trunk.
> >     2-4. back to 2-1.
> 
> preferably 2, as I'm planning on doing a doozy on trunk.
> 
> 2-3 would be for the 1_8 branch.

OK. I'll use 2.

Thanks,
--
kou

In This Thread

Prev Next