Stick with 2.1.4 -- not ready for prime-time - jeffsters1
I didn't notice the 1-star, I will agree that's harsh and would go further to say it should have been a comment rather than a review. I will also agree that the user should report this issue and any log files to the developer. While the users words "ready for prime time" are misplaced, I still do not agree that, unless the problem is isolated, a beta should so easily crash or fail to work. We can't usually even declare beta with a known crasher in regression and the build needs to be feature complete or the offending feature pulled. I'm not implying that this was done only that THIS user seemed to run into issues fairly quickly, where there were none for him before, which should be cause for concern to anyone thinking of using the beta to address the fixes listed. Thanks.
Existing users, log in. New users, create a free account. Lost password?
Stick with 2.1.4 -- not ready for prime-time - jeffsters1
I didn't notice the 1-star, I will agree that's harsh and would go further to say it should have been a comment rather than a review. I will also agree that the user should report this issue and any log files to the developer. While the users words "ready for prime time" are misplaced, I still do not agree that, unless the problem is isolated, a beta should so easily crash or fail to work. We can't usually even declare beta with a known crasher in regression and the build needs to be feature complete or the offending feature pulled. I'm not implying that this was done only that THIS user seemed to run into issues fairly quickly, where there were none for him before, which should be cause for concern to anyone thinking of using the beta to address the fixes listed. Thanks.Reply to This | Parent
Monday, September 14 2009 @ 05:58 PM PDT