I didnt expect it to be stable like a release version, but i expect bugs to
be solved ... And still ... betas are the only way to get features
others have some time.
> debug it, send a bug report to support@livingston.com, with as much
> detail as possible. Traditionally, beta testers are required to make
Did that - No answer. Dont tell me to call ... i am in Europe - this
is a bit a problem.
> reports on the operation of the software... Livingston doesn't require
> this with their open betas, but this sort of bitching and whining puts
> open betas at risk! I wouldn't blame them for requiring authorization
> for betas, given the amount of complaining that is going on with this
> current batch.
> Traditionally, beta software has features frozen, so things generally
> become more stable with each realease, but in this case they needed
> to add V.90 support (a NEW feature) in b15, so it is expected that
> more problems will occur.
> Again, if yout can't deal with unstable software, don't run prerelease
> versions!
I reported the reboot problem to livingston 48 hours after b15 came out
and b17 still contains the bug ... *hmm* ..
Why do i report bugs when they do not get fixed ? - even no communication
to get closer to the bug.
I get more and more the feeling, when leaving the OpenSource sector
you get hopelessly lost, nobody will fix bugs FOR YOU, you have to
do it on your own.
Flo
-- Florian Lohoff flo@mini.gt.owl.de +49-5241-470566 - 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/>