> I think you are missing the point here. There is no way that in 60
> days that there has not been any advances made in the beta software that
> could not be released in a new open beta.
Are you a Lucent developer? Are you in contact with the developers to the
extent that you are aware of the progress they are making on each part of
the code that needs work?
If you are making the above statement, you obviously have not done too
much software testing. The point isn't to release new code every time an
advance is made (new feature or bug fix), but to release new code when an
advance that is made that simultaneously doesn't cause other problems.
One step forward and two steps back is useless, and doesn't do much except
make people look silly and waste their time.
> I don't think anyone expects BETA software to perform flawlessly, it
> should be functional (and 3.8b15 is.) The statement of DON'T EVER USE BETA
> SOFTWARE is rediculous. There are those of us who do, and we know that we
> are taking a certain amount of risk into our own hands. BETA software
> becomes production software through testing and dare I say bitching about it
> as well.
How about this statement:
Don't ever use beta software if 1) you don't have a suitable environment
to test it in or 2) you don't feel like dealing with problems that might
be caused by the beta, even if you do have a suitable environment.
-- Scott M. Drassinower scottd@cloud9.net Cloud 9 Consulting, Inc. White Plains, NY +1 914 696-4000 http://www.cloud9.net- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>