From: "URABE Shyouhei" <shyouhei ice.uec.ac.jp>
>
> [...] ruby_1_8 branch has been far
> developed from the point of 1.8.5 release. Releasing
current ruby_1_8 is
> not a wise idea.
Just yesterday I compiled ruby from the ruby_1_8 branch,
because I wanted
the array.c memory leak fix, and it's a post-1.8.5 revision.
My (incorrect) assumption was that the ruby_1_8 branch would
mean
"latest stable" code for ruby 1.8.
> (1) Ruby development goes into three-branch-model (like
branches in *BSD
> world):
> - CURRENT branch: trunk (currently ruby 1.9)
> - STABLE branch: ruby_1_8 branch that exists now
> - RELEASE branch: new branch to only adopt bug fixes
This nomenclature seems a little confusing, because if
releasing curernt
ruby_1_8 is not a wise idea, why would we call it STABLE ?
I guess STABLE makes sense when comparing 1.8 to 1.9, but,
really it
sounds like ruby_1_8 is a development branch.
How about creating a ruby_1_8_dev branch, and do the ongoing
1.8
development in that branch, and leave ruby_1_8 as the
stable/release
branch?
Regards,
Bill
|