I've never seen a bug list for any software I've ever used
> On Aug 27, 2015, at 11:48 AM, [email protected] wrote: > > Reasonable and understandable on future product direction but not on known > and acknowledged software bugs. Not having a list wastes everyone's time. > > Adrian > > > Sent from my android device. > > -----Original Message----- > From: "Brian L. Lightfoot" <[email protected]> > To: [email protected] > Sent: Thu, 27 Aug 2015 3:27 PM > Subject: RE: [LegacyUG] Bug items List (used to be Same sex Marriages) > > A few months back I asked on this forum if Legacy has available a list of > outstanding bugs. The reply was to the effect that they would never consider > making public such a list because it was considered proprietary information > and might give competitors an edge. I wanted to reply that it was a common > task among many software products but I felt like I was being browbeaten and > the discussion ended there. > > Brian in CA > > > From: [email protected] [mailto:[email protected]] > Sent: Thursday, August 27, 2015 1:50 AM > To: [email protected] > Subject: Re: [LegacyUG] Bug items List (used to be Same sex Marriages) > > I have never known software or firmware where you cannot find a known problem > list, somewhere (ie readme files). As a database developer, programmer and > support manager of some 25 years that was standard requirement of me. I am > not talking here of new developments but rather of known existing bugs. I > would not put a fix date much to annoyance of various people but there was a > list of known bugs available to users. > > Priorities are what appears wrong here. I would suggest they should be. > > 1. Fix bugs which cause Legacy to crash or freeze. I have one of these > outstanding. After 2 years there should be none of these. > > 2. Fix bugs which didn't happen in 7 but happen in 8. Have 2 of these > outstanding. After 2 years there should be none of these. > > 3. Fix bugs which cause data to appear incorrect or missing with certain > settings. Had one of these fixed in last release. > > 4. Fix situations where Legacy cannot store data re relationships between > persons which other genealogical programs can. > > 5. Fix report formatting problems. > > 6. Fix any other problems. > > 7. New developments including next major release. > > No reported problem should remain unfixed or patched for longer than 6 months. > > I did once use FTM, the major reason I left was they didn't fix bugs until > next major release, which you had to pay for. Then after paying for an > upgrade the bug was still there. Legacy don't follow the same route. > > Please note I am not knocking Legacy here as I still consider it is one of > the best available. It used to be the best. However it appears 8 was released > before it should and that not enough testing was done. This has caused the > problems we are now seeing. I never ever found bugs in 7. For those > suggesting a downgrade, it's not that easy in terms of ensuring data > integrity when you have in excess of 7000 individuals. > > Regards > > Adrian > > > Sent from my android device. > > -----Original Message----- > From: Dave Keeney <[email protected]> > To: [email protected] > Sent: Thu, 27 Aug 2015 3:47 AM > Subject: [LegacyUG] Bug items List (used to be Same sex Marriages) > > I wanted to respond to this issue but agree it should not be included within > the "Same sex Marriages" thread. I've copied a few of the latest comments and > started this new thread. > > Not being able to view the known problems list has been a big concern to me > for a long time. > > Re: "It's not secrecy at all". > It sure feels like it's a secret when we can't see the status of problems. > > I've submitted several bugs that have been acknowledged. And I still do not > know any of their statuses. Some of them are so old that I sometimes forget > I've submitted one and do so again, only to be told that it's already in > process. > > I also agree that everyone has bugs that are causing them grief. I've got one > that causes me many hours of extra work monthly. But it's my dealing with a > One Place study that probably doesn't rear its head to most people. So I > agree with the "you can't please everyone all the time". > > My only recourse has been to find workarounds, a lot of times dealing with > just using the Access database which works for now but I'm sure sooner or > later it will come back to bite me by using it. Legacy is under no > expectations from me to tell me when they change things under the covers so > sooner or later I'll probably pay. > > Re: It's frustrating but still the best. > I agree with this 100%. Programming puts developers in a sticky situation, a > lot of times in a "no win" "no win" situation. > > So I appreciate Legacy's efforts, and will continue to find whatever > workarounds I can find for bugs and live with them as long as I can. > > But it would be a lot easier just to know the status of them ... even if it's > LOW priority because nobody else as chimed in with that bug. > > And because of this I no longer submit bugs that I find. > > Dave > > -----Original Message----- > From: I Macaulay <[email protected]> > To: [email protected] > Sent: Wed, 26 Aug 2015 9:34 PM > Subject: Re: [LegacyUG] Same sex Marriages > > Its not always to my advantage to update the program, but I am sure that > there is value behind the changes. I for one trust Legacy.. They have > proven that they care more than once. > > Frustrating at times but still the best. > > Ian > > I used to be a banker, but then I lost interest. > > Ian Macaulay Carp, Ontario > Open at 10:AM Close at 5:00 PM > 45.2397 N long: 76.0991 W Elv 137 M UTM > Don't Forget to Save the Stamps > > From: "[email protected]" <[email protected]> > To: [email protected] > Sent: Wednesday, August 26, 2015 3:38 PM > Subject: RE: [LegacyUG] Same sex Marriages > > It is secrecy. The bug list is not publicly available. Let's get version 8 > working correctly before worrying about 9 or are we going to 10 as Microsoft > did. Legacy 7 et al was fine. 8 appears to be full of problems. I for one > wished I hadn't upgraded as I am not sure what I got apart from numerous > problems. > > Adrian > > Sent from my android device. > > -----Original Message----- > From: Jim Terry/Support <[email protected]> > To: [email protected] > Sent: Wed, 26 Aug 2015 8:13 PM > Subject: RE: [LegacyUG] Same sex Marriages > > Adrian, > > It's not "secrecy" at all. Some changes like allowing same sex > relationships/marriages affect many aspects of Legacy, like reports, > events, file maintenance, etc. It takes time and testing. I presume things > that crash Legacy and affect the largest numbers of users probably get the > programmer's first priority. In addition, the programmers are always > thinking ahead to the next version while trying to work on things in the > current version. We have a bug tracking system as well as a list of > suggestions made by users that the programmers make use of. I image that it > all can get complicated. So we never know how long beta testing will take > and what issues testers might find. > > Jim > Technical Support > Legacy Family Tree > > > -------- Original Message -------- > > From: [email protected] > > Sent: Wednesday, August 26, 2015 11:55 AM > > To: [email protected] > > Subject: RE: [LegacyUG] Same sex Marriages > > > > Jim > > > > You summarise what the problem is so far as the end user is concerned. We > have no information as to when bugs will be fixed. 2 years is far too long! > We don't understand the process for prioritisation of bugs. From looking at > version fix lists some of the things fixed are very obscure and at the same > time obvious problems as this are ignored or appear to be. I believe I have > reported 5 bugs and I believe only one is fixed and that was one that was > previously known about. Why all the secrecy about bug fixes and anticipated > fixes. > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://support.legacyfamilytree.com > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on > our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://support.legacyfamilytree.com > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on > our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
