n" <[EMAIL PROTECTED]>
To:
Sent: Thursday, November 29, 2007 8:16 AM
Subject: Re: [LegacyUG] Old Issue with Unwanted Punctuation (Period)
If you download and install the updates, why in the world do you need a
list of the items dealt with in the updates. If the :"bug" still exists
I don't see what Richard's respsonse has to do with my comment.
- Original Message -
From: "RICHARD SCHULTHIES" <[EMAIL PROTECTED]>
To:
Sent: Thursday, November 29, 2007 7:46 PM
Subject: Re: [LegacyUG] Old Issue with Unwanted Punctuation (Period)
But in m
But in many cases, fixes have been reported by more
than one person, simultaniously. Who gets the note, or
do they all get one. Who keeps track of that list. I
hope they spend the time fixing the program instead of
sending thank you notes as the last part of a fix. I
have sent requests to MS and th
Hi Dev,
Generally the person who reports a bug is notified when it is fixed.
This isn't done automatically so there are some slip ups. Also it
probably doesn't happen for everyone who reports a bug - just the
first person whose details are attached to the bug report.
Cathy
At 02:29 AM 30/11
AIL PROTECTED]>
To: LegacyUserGroup@legacyfamilytree.com
Sent: Thursday, November 29, 2007 10:16:11 AM
Subject: Re: [LegacyUG] Old Issue with Unwanted Punctuation (Period)
If you download and install the updates, why in the world do you need a list
of the items dealt with in the updates. If the
I've been on both sides of software updates (programmer writing fixes;
system administrator trying to ensure a new release doesn't break anything
critical to a 24/7 operation).
My experience is that *very* few people ever read a detailed "fix list" if
it's more than a couple of pages. As a system
> Not all of the changes are applicable to all the "regional versions" [my term
> by
> which I do not mean language]. For example in the UK and certain other
> versions,
> for reports instead of reading "died at age" it now reads "died aged". Do you
> seriously expect changes in wording for *all*
If you'd just download and install every update oh, well, never mind ;-)
- Original Message -
From: "Dev Null" <[EMAIL PROTECTED]>
To:
Sent: Thursday, November 29, 2007 12:29 PM
Subject: Re: [LegacyUG] Old Issue with Unwanted Punctuation (Period)
If you dow
: Thu, 29 Nov 2007 09:29:10 -0800
> From: [EMAIL PROTECTED]
> Subject: Re: [LegacyUG] Old Issue with Unwanted Punctuation (Period)
> To: LegacyUserGroup@legacyfamilytree.com
>
>> If you download and install the updates, why in the world do you need a list
>> of the items
> If you download and install the updates, why in the world do you need a list
> of the items dealt with in the updates. If the :"bug" still exists, it
> wasn't fixed, if the "bug" has gone away, then it has been fixed. I'ts
> inclusion on a list makes no difference one way or the other.
I don'
> Every update should include a list of ALL changes since the previous update
> and
> should NOT be released until that list is included in said update-period.
I've got to think that this info is in at least two places already...
1. They use MANTIS for tracking things, so a report could be pulle
ce one way or the other.
Tom
- Original Message -
From: "Wynthner" <[EMAIL PROTECTED]>
To:
Sent: Thursday, November 29, 2007 11:02 AM
Subject: Re: [LegacyUG] Old Issue with Unwanted Punctuation (Period)
Perhaps it isn't a high priority task for them...but it darn well
: [LegacyUG] Old Issue with Unwanted Punctuation (Period)
> Is
> there any particular reason why the published list of changes CANNOT be
> COMPLETE so that we only need to check problems once, after they are
> supposed to have been fixed?
I would think this would require litt
Honestly, as a computer software developer (not for Legacy), It is
pretty much unheard of to list every single change that has gone into
a release - especially something like a single period being printed
where it should not. In any software program, for each release, there
is often hundreds of ch
> Is
> there any particular reason why the published list of changes CANNOT be
> COMPLETE so that we only need to check problems once, after they are
> supposed to have been fixed?
I would think this would require little extra effort now that the developers
have their new system for tracking b
IL PROTECTED]>
To:
Sent: Wednesday, November 28, 2007 1:00 PM
Subject: RE: [LegacyUG] Old Issue with Unwanted Punctuation (Period)
Kay,
Using the most recent build of Legacy 6.0.0.168, I just created a test
source and entered your example in the Source Detail exactly as you showed
in your exampl
Sherry/Support wrote:
Without downloading updates, you have no way of knowing if a problem has been
fixed or not.
Unfortunately, you are quite correct. Looking at the published list of
changes for each release gives us only a clue as to SOME of the changes
that have been made. We have t
Kay,
Using the most recent build of Legacy 6.0.0.168, I just created a test
source and entered your example in the Source Detail exactly as you showed
in your example and the output does not include a period. The output is
exactly the way I inputted the data.
Same with entering that line in Publ
h" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, November 28, 2007 12:27 PM
Subject: RE: [LegacyUG] Old Issue with Unwanted Punctuation (Period)
Hi Kay
The issue appears to be fixed, I am using the latest build (November 6).
You
may need to think about upgrading after all:-)
Source Det
Hi Kay
The issue appears to be fixed, I am using the latest build (November 6). You
may need to think about upgrading after all:-)
Source Detail
Entry: Joe Blow death certificate #12345 (1939)
Results: Joe Blow death certificate #12345 (1939).
Master Source Example:
Entry in Title: Joe Blow
20 matches
Mail list logo
