Re: Test::Unit maintainer

Hi,

In <1F08809E-7875-462E-AB81-11BA07D6048Dzenspider.com>
  "Re: Test::Unit maintainer" on Sat, 22 Mar 2008
09:04:24 +0900,
  Ryan Davis <ryand-rubyzenspider.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