Re: (ASCEND) Ascend Patch 5.0ap23?

To: Matt Holdrege <matt@ascend.com>
Subject: Re: (ASCEND) Ascend Patch 5.0ap23?
From: "Alex.Bligh" <amb@xara.net>
Date: Mon, 08 Sep 1997 23:50:56 +0100
cc: Craig Salmond <salmond@unix.cde.com>, "Nolan W. Bailey, Jr." <nolan@cp-tel.net>, ascend-users@bungi.com
In-reply-to: Your message of "Mon, 08 Sep 1997 12:48:11 PDT." <3.0.3.32.19970908124811.00725a90@darla.ascend.com>
Sender: owner-ascend-users@max.bungi.com

 
> We've done this several times in the past. There is precedence when it is
> possible that the software could be harmful to operations. Folks who do
> billing based on radius accounting could possibly be affected.

Oddly with p20 you didn't do this, you put up a warning README, and
that was far more broken accounting wise.

Also you didn't do this with every other release (certainly in the
5.x bugs) which even Ascend acknowledges has fatal bugs in.

Perhaps you could elucidate on what QA Ascend do before they make
releases, how they decide when to incorporate bug fixes, and what sort
of response we should be hoping to get from Ascend in terms
of time from [reporting fatal bug with no work around] to [Ascend
acknowledge bug] to [Ascend fix bug] to [bug fixed version gets
released to customer]. People in Europe would love to know. That's
customers, your own account managers, and your competitors.

Alex Bligh
Xara Networks

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

References:

Re: (ASCEND) Ascend Patch 5.0ap23?

From: Matt Holdrege <matt@ascend.com>

Prev by Date: Re: (ASCEND) Ascend Patch 5.0ap23?
Next by Date: Re: (ASCEND) Be careful with 5.0Ap23!
Prev by thread: Re: (ASCEND) Ascend Patch 5.0ap23?
Next by thread: Re: (ASCEND) Ascend Patch 5.0ap23?
Index(es):
- Main
- Thread