Takeover Example

Thread View: comp.sys.mac.oop.macapp3

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Research SW Design, D Goldman,PR... Sun, 27 Dec 1992 21:20

#35

Author: Research SW Design, D Goldman,PR...
Date: Sun, 27 Dec 1992 21:20

42 lines
2072 bytes

Dear MacApp'ers --
 
Regarding my accompanying link ("TEditText Bug")...
 
I would speculate that this is a bug whose fix will:
 
(a) involve a very slight change to the MacApp code;
(b) easily be seen to not have distant side-effects;
(c) at best show up in an Apple bug doc, and that only if we're unexpectedly
lucky (Kent says he's being transfered to another engineering department!);
(d) belong in MacApp 3.0.2 (which there is no indication we will ever see Apple
create or distribute).
 
If Apple supported MacApp 3.0, then this is what would happen now:
(1) Apple confirms and repairs this very small and easy bug.
(2) The fix is made to MacApp 3.0.2, which is distributed on ETO #10.
 
Since Apple no longer supports MacApp 3.0 [Go ahead: prove me wrong! Follow
the above 2 steps.], let us suppose that MADA buys it. Then here is the
scenario:
 
(1) I, or someone else, figures out the fix and posts it here. One or two other
active MacApp'ers who could be personally affected by this bug check to confirm
that the fix looks right to them.
 
(2) MADA's hired, full-time (if necessary) MacApp maintainer examines the
proposed fix, and if all still agree that it looks okay, makes the change to
the MADA master copy of MacApp.
 
(3a) The revised MADA master is distributed on the next quarterly MADA MacApp
CD-ROM, to which those of us who are actively using MacApp have subscribed.
 
-or-
 
(3b) The revised MADA master is distributed on Apple's ETO #10. (Apple paying
part of our ETO subscription price [the part previously going to support MacApp
support] to MADA as a licensing fee.)
 
 
-- Dave Goldman
   Research Software Design

Re: Takeover Example

#42

Author: Kent Sandvik
Date: Mon, 28 Dec 1992 00:16

43 lines
2605 bytes

In article <725492228.1473624@AppleLink.Apple.COM>, RSD@AppleLink.Apple.COM
(Research SW Design, D Goldman,PRT) wrote:
> Regarding my accompanying link ("TEditText Bug")...
>  
> I would speculate that this is a bug whose fix will:
>  
> (a) involve a very slight change to the MacApp code;
> (b) easily be seen to not have distant side-effects;
> (c) at best show up in an Apple bug doc, and that only if we're unexpectedly
> lucky (Kent says he's being transfered to another engineering department!);
> (d) belong in MacApp 3.0.2 (which there is no indication we will ever see Apple
> create or distribute).
>  
> If Apple supported MacApp 3.0, then this is what would happen now:
> (1) Apple confirms and repairs this very small and easy bug.
> (2) The fix is made to MacApp 3.0.2, which is distributed on ETO #10.
>  
> Since Apple no longer supports MacApp 3.0 [Go ahead: prove me wrong! Follow
> the above 2 steps.], let us suppose that MADA buys it. Then here is the
> scenario:

I just want to raise one issue, Q&A of a product is a very expensive
phase, and in the case of MacApp we are even dealing with a multitude
of testing cases. In other words one engineer for testing/maintenance
is maybe OK, maybe not (I'm skeptical but I might be wrong, if you find
someone willing to hack 20 hours a day :-) ).

I've seen this problem over here in DTS, where we have people, resources,
even a lot of equipment. The problem we have is time, it takes a lot of
time
and energy to test out bug fixes, and we don't have the infrastructure
concerning a full SQA process, something that needs to be in place day
one concerning bug fix releases. In addition, you have to be very, very
sure that bug fixes are properly working, because developers don't like
sudden updates to bug fixes (yes we know, we sometimes have the same
QA problem over here).

Cheers,
Kent
-------------------
Kent Sandvik (UUCP: ....!apple!ksand; INTERNET: ksand@apple.com)
DISCLAIMER: Private activities on the Net.		
"Don't just do something!  Stand there!"  -- Mystery Science Theater 3000

Hello, but I must be going...

#43

Author: Kent Sandvik
Date: Mon, 28 Dec 1992 00:24

28 lines
1959 bytes

In article <725492228.1473624@AppleLink.Apple.COM>, RSD@AppleLink.Apple.COM
(Research SW Design, D Goldman,PRT) wrote:
> (c) at best show up in an Apple bug doc, and that only if we're unexpectedly
> lucky (Kent says he's being transfered to another engineering department!);

Hi, I guess I need to clarify what is going on. I'm leaving DTS, because
I will take part in the startup of the PIE Newton DTS group. Expect
postings
from me concerning MacApp to (fortunately :-)) diminish in two weeks'
time.

Just to stop any rumors about this all, DTS has two fully qualified
MacApp engineers. Also, our core technology front line group now
has engineers that know about MacApp and OOP. In addition, DTS will
fill my position as soon as possible with a similar candidate. So 
from MacApp support point of view the situation is fully under control,
and this was a perfect time for me to move on to new challenges.

Have fun, and I'm sure we will meet again concerning Newton and PIE
products! Unfortunately I couldn't make it concerning MADACon, and 
that was sad, because last year's MADACon in Florida was one of the
funniest computer conferences I've attended.

Kent
-------------------
Kent Sandvik (UUCP: ....!apple!ksand; INTERNET: ksand@apple.com)
DISCLAIMER: Private activities on the Net.		
"Don't just do something!  Stand there!"  -- Mystery Science Theater 3000

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads