Dennis, "With every release I test each bug to see if it's been fixed."
A practice which, unfortunately, is necessary, since we can't count on it. But, do you also test on the releases AFTER it's been fixed, since some old buggy code has managed to reappear later? "So I do hope we see a concentrated effort to fix the reports (and other bugs) before moving on to V6 development and new bells and whistles." I couldn't agree more! As a little kid I liked to play with bugs, but now as an adult I don't want anything more to do with them. Whenever V6 is released, I may download the free version to a test system to play with, but there is no way I'll pay for it or actually use it for real until after monitoring this list for a couple months. I'll be looking for two main things. 1. Every previously reported bug up through V5 has actually been fixed. 2. All new features of V6 have been thoroughly tested BEFORE release so that they can all be depended upon to work reliably all of the time. Without both of those things happening, I'll be shopping elsewhere. People who work in IT are well paid to test their systems and the aggravation of customers being treated as guinea pigs gets to be too much after a few years. I've been "lucky" enough to not depend on reports so far, since I've been mostly doing research and gathering data. But even with the occasional ancestor book or descendant book that I preview on screen in order to check my data I've run into some scary looking stuff. I'd never print those things out to distribute to family -- they might stop cooperating with my questions if they thought that was the best I could with all their information. Bob Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
