On Friday, September 21 2001 12:50:31, Patrick Campbell-Preston wrote:
[...]
> There isn't really much alternative anymore. The choice seems to be
> either bleeding edge, or dulled rusty edge encrusted with dried blood;
> when did we last have an actual 'release' which wasn't broken in at
> least one major area of functionality?
That is somehow right.
Probably there should be two CVS branches: a development
branch and a release branch. One that gets only bug fixes
and another one which gets new features and testing before
it gets into the released version. Well that is how it is
done for most bigger code bases and it seems time to do that
also for BBDB.
Wasn't that already suggested some while ago?
[...]
> One possibility I have toyed with (but not very seriously; if I had
> the time and energy I could just fix all the new bugs as they arise,
> couldn't I!) is of making a cut-down version of BBDB by throwing out
> any functionality which seems to be superfluous (to me!), trying to
> rewrite any implementation which seems to be too unmaintainable, and
> putting some more serious effort into testing and defining the
> behaviour.
>
> Maybe a more practical course of action would be to split the
> distribution into a bbdb core (with a stable API) and the rest?
That would be great, but who has the time for doing that?
Or is Waider doing that by now? ;)
Robert
_______________________________________________
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
