From: Peter C. <pc...@ca...> - 2001-01-04 17:47:25
|
At 09:14 AM 04/01/01 -0800, "Robert Rainwater" <rra...@ya...> wrote: ><snip> >I would be hesitant to post a link on the site, since most developers and >testers are subscribed to this list. Putting a link on the site would cause >people to download it and use it as final code. > >Robert Rainwater But what choice is there? The current "release" is nearly two months old. We know there have been a tremendous number of bug fixes, enhancements, and style changes since then. People really only have a choice of using a very old and substantially obsolete "release," or the current code. This is not meant as a criticism - obviously, this is free code, people are doing the best they can, following their own priorities, etc. But the fact remains that releases aren't happening, and are very difficult to arrange in this style of development. Unless the developers institute such practices as code freezes, bug-fix-only periods, extensive testing, etc., there is never likely to be a "stable" version for use as a new release. This type of development will always have segments under active development (until the code becomes obsolete and development stops). Unless you are planning some kind of active process to bring about a stable code package that can be a new release, the new code is really all that is available. -- Peter Curran Software Developer Casebank Technologies Inc. pc...@ca... 905 792-0618 X535 |