Rubyinstaller devel - Apr 2004 - Proposal for Release Candidate Testing

I find the bugs being reported with the batch files (bad paths) and rdoc/ri
a little embarrassing as I thought I had fixed this (at least I thought I
fixed the paths).

I think that, in future, it would be a good idea to post release candidates
to the ruby-talk list for general testing. That way we can correct problems
like this *before* the release.

Comments?

Curt

On Tue, 2004-04-20 at 09:09, Curt Hibbs wrote:
> I think that, in future, it would be a good idea to post release candidates
> to the ruby-talk list for general testing. That way we can correct problems
> like this *before* the release.
Sounds okay to me.

Let those early adopters take the arrows in the back :-)

/\

Curt Hibbs wrote:
>I find the bugs being reported with the batch files (bad paths) and rdoc/ri
>a little embarrassing as I thought I had fixed this (at least I thought I
>fixed the paths).
>
>I think that, in future, it would be a good idea to post release candidates
>to the ruby-talk list for general testing. That way we can correct problems
>like this *before* the release.
>
>Comments?
>  
>
I guess none of the beta peoples ran across this?

My vote would be no special names on new releases, but that we don''t 
designate one as being the stable one until it''s proven itself stable. 
Right now 180-10 should be indicated as ''stable'', and 181-12
as ''latest''.

-- 
Chris
http://clabs.org

Chris Morris wrote:
> 
> My vote would be no special names on new releases, but that we
don''t
> designate one as being the stable one until it''s proven itself
stable.
> Right now 180-10 should be indicated as ''stable'', and
181-12 as ''latest''.
I like it!

Curt

On Tue, 2004-04-20 at 10:57, Curt Hibbs wrote:
> Right now 180-10 should be indicated as ''stable'', and
181-12 as ''latest''.
> 
> I like it!
d''accord.

Curt Hibbs wrote:
>
> I find the bugs being reported with the batch files (bad paths)
> and rdoc/ri
> a little embarrassing as I thought I had fixed this (at least I thought I
> fixed the paths).
>
> I think that, in future, it would be a good idea to post release
> candidates
> to the ruby-talk list for general testing. That way we can
> correct problems
> like this *before* the release.
FYI -- I''m trying to fix this stuff this weekend and put out a release
candidate for general testing. I really want to get a *stable* version of
1.8.1 released as soon as possible.

Besides just being a good idea, in a couple weeks I''m closing on buying
a
new house and along with planned renovations (I''m the handyman-type
that
does his own home improvement work), and other family commitments, I
probably won''t be doing any more significant work on the Ruby Installer
for
the next few months.

There''s also a reported problem with win32ole that I''ll look
at (but I may
not be able to do any thing about it).

Curt