From: Luis Lavena <luislavena@...>
Date: 2010-08-06T03:47:24+09:00
Subject: [ruby-core:31628] Re: Release engineering status of 1.9.2-p0

2010/8/4 Yusuke ENDOH <mame@tsg.ne.jp>:
> Hi,
>
> I'm reporting the status of 1.9.2-p0 release which has been planned at
> early this month.
>
>
> �(1) backports from trunk into ruby_1_9_2
> �(2) busyness of the release manager
>
>
> (1) Currently, we have roughly backported patches that was committed by
> 23 Jul.
> In principle, I will no longer backport any patch for 1.9.2-p0.
>
> A brand-new patch should have a certain amount of "soak time" in trunk.
> *Almost all* patches that have just been committed into trunk are not
> stable yet. �They may often cause another issue, or may not been fixed
> completely. �Backporting such patches will never stabilize ruby_1_9_2
> branch. �In fact, I actually had some trouble about one patch that
> requires another patch that requires another patch... (about 5 times).
> I think this lesson (soak time) should be applied in the next release.
>
> Meanwhile in this time, I decide that I will backport only patches that
> meat any following conditions:
>
> �- SEGV or [BUG] problem on supported platform
> �- build failure on supported or besteffort platform

Bug #3637 block certain versions of mingw32 under cross-compilation
(mingw and mingw-64 projects)

r28835 fixed this.

I'm building current branch with GCC 4.5.0 for RubyInstaller, will
provide any feedback on build failures that will require adjustments.

Thank you.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup�ry