2011/8/23 Michal Suchanek <hramrach / centrum.cz>:
> On 23 August 2011 13:20, NARUSE, Yui <naruse / airemix.jp> wrote:
>> (2011/08/23 20:09), Lucas Nussbaum wrote:
>>> On 23/08/11 at 06:50 +0900, SASADA Koichi wrote:
>>>> (2011/08/10 7:18), Yukihiro Matsumoto wrote:
>
>>> I think that you should inspire from the release management of Linux
>>> 2.6, and use one-branch-per-feature rather than one-branch-per-release.
>>> Then, you could have a single integration branch (that would most likel=
y
>>> be trunk), and make releases from this branch, since features will have
>>> time to mature a bit inside feature branches.
>>>
>>> Using shorter release schedules would also probably help. The addition
>>> of new features will be more incremental (less new features per
>>> release), which will also reduce the stabilization periods. Several
>>> important projects now use a 6-month release cycle. Maybe that could
>>> work for Ruby too?
>>
>> You don't want patch release?
>
> If you use Linux for comparison you can see that it has patch releases.
>
> They have 2.6.N released from trunk and backport fixes to 2.6.(N-1).n.

Hmm, thanks for explanation.

As far as I understand, current Ruby's development model is the same one
except the fast release cycle.

--=20
NARUSE, Yui =A0<naruse / airemix.jp>