[CF-Devel] TODO List - Flamebait

[Jan Echternach]

On Thu, Nov 09, 2000 at 08:45:07AM +1100, John Cater wrote:
>
     
      Firstly, the repository is being used to fix bugs in the last release -
     
     >
     
      fine and good. But it is also being used to "test" new features (an
     
     >
     
      example is the race/class split). Is this the best way?
     
     
It's much easier than fixing each bug twice:  Once in the stable branch,
and once in the development branch.  Furthermore, many bugs are fixed
as new code replaces old code.

If something is wrong with a new feature that's already in the CVS,
there are two options:  Deferring a release until the feature has been
fixed, or removing/disabling the feature again.  New features in
official releases contain rather few bugs, most bugs that I fix are
bugs in old code.  I think implementing new features is at least as
important as fixing new bugs because the TODO list is still very long.

>
     
      Actually what I would like is a "feature freeze" of the current CVS,
     
     >
     
      leaving it only open to bug fixes with the focus on a "stable" 0.96
     
     
I doubt that a feature freeze would help much with making a stable
release.  Right now, a code review is more efficient because only
little code is aware of that any non-trivial function call can destroy
or move almost any object.  I think the most likely cause for a server
crash is still that an object is destroyed after putting it on a map.

-- 
Jan