I'm not talking about 2.2. I'm talking about a severe slowdown in the
pace of development on this entire project.
And it sounds like you've been feeling the effects of all the red tape
too, with being fed up trying to follow through with a release.
There are two separate issues:
* The difficulty in *producing* releases is due to RMs being too afraid
to make releases that aren't perfect. This phobia is a disease,
because
it prevents the release-early-release-often motto from happening.
* The difficulty in *making progress toward a releasable repository* is
being caused by the STATUS file bottleneck. The STATUS file
bottleneck
is caused because we have Review-Then-Commit rules set up, which
means everyone has to serialize EVERY CHANGE on that file. (You're
talking to the thread programming guy here, remember? That's a point
of contention. :)
(It's interesting to note that SVN is a parallel development version
control engine, but RTC forces us to serialize all our changes.
Maybe
we should start using SCCS.)
RTC came with good intentions (higher quality code), but it's clear now
that it's not working and it needs to change.
-aaron
On Aug 9, 2005, at 9:47 AM, Justin Erenkrantz wrote:
--On August 9, 2005 8:17:37 AM -0700 Aaron Bannert
<[EMAIL PROTECTED]> wrote:
I've been trying to speed up the release cycles for years, but
it's only gotten slower with all the red tape.
Where have you been when we've done releases in the last few years?
The slow release cycles are just another symptom of a broken process,
they are not the cause.
If you want to place a cause on why 2.2 hasn't been released, I
feel that there is only one real reason. I gave up on trying to do
2.1/2.2 releases because I got fed up with having every release
blocked for illegitimate reasons. Paul ran into the exact same
roadblocks; but he's probably too nice to admit it.
The 'slow release cycle' has *nothing* to do with CTR or RTC. --
justin
