> -----Original Message-----
> From: Bernino Lind [mailto:[EMAIL PROTECTED]]
> CURRENT branch is a continues function of development,
> meaning a "release"
> of current is never intended. The code to be released is
> first backported
> into STABLE and when all the code has proven super super
> stable for a couple
> of months it is RELEASEd...
Hi.
I don't think that this 'debian-style' approach is the best way - a lot
of backporting will be slow and can cause many problems (Packagers' rule
: every copy & paste will introduce at least one typo). also its nearly
impossible to do major architecture changes this way.
My suggestion is to follow the standard way of developing and branching
large scale projects, as seen on KDE and Mozilla: at a set date the tree
is frozen and branched. from that point no new features are introduced
into the new branch and only bug fixing is done on it. then when the
state of the new branch is deemed stable enough, it is released. in the
mean time new features can be introduced on the main trunk. if bug fixes
(and only bug fixes) in the main trunk are deemed benefeicial to the
"release" branch they can be back ported. when a new release is needed,
the main trunk is frozen and branched off again, the old "release"
branch abandoned and bug fixing is only done on the new "pre-release"
branch.
AFAIK this is how Kannel used to be developed, before all the old
releases were abandoned.
Oded Arbel
m-Wise Inc.
[EMAIL PROTECTED]
--
C++ is the only current language making COBOL look good.
--Bertrand Meyer
