On Sep 21, 2007, at 1:23 PM, Costin Manolache wrote:
I'm a bit confused - what happens with the trunk then ? Usually the
trunk will become the new release - or the code from the trunk will
somehow
get released.
There are 2 ways for code in trunk to get released:
1. trunk, the whole kit and kaboodle becomes a release
branch. For this to happen, RTC comes in and the
PMC and dev community agree that trunk should serve
as the basis for TC X.Y.
2. Parts of trunk end up in releases. For this
to happen a patch is proposed for backport to
a release branch under RTC rules. Normally, this is
noted and voted on in a STATUS file.
trunk continues to be operated under CTR, but all code *from*
trunk that goes into a release branch is via RTC.
But forget the release/trunk details - the question is how to
determine the
goals or direction - things like should use switch coyote to nio,
should we
change the API in one way or another, how much backward
compatibility to
preserve, what to deprecate and what to bundle by default. Doesn't
matter
where
it happens - the reason we have this conversation is because this
kind of
decision was made by one or 2 people fighting each other and without
enough consensus - instead of the broader community.
Both Remy and Filip ( and quite a few other people actually ) are
quick to
express their disapproval for something or their goals - and maybe
sometimes
too blunt
and personal.
The proposed processes ( with their evident flaws ) are intended
to make it clear that neither of us 'decides' ( by veto or by
sumitting
something ) -
either we have a consensus ( everyone agrees ), or at least the
typical 3
+1 and
majority.
All good points. It just seems to me that the voting should be
on code that, as you said, affects people. When the code enters
a release branch, then approval is needed. The fact that it's
been in trunk and has worked well and that others within
the PMC and dev community have played and worked with it
will count for something, but it is still a RTC rule. Having
trunk means we get consensus twice: the 1st under CTR (a lazy
consensus to be sure) and then when moved to release under
RTC.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
