Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) Max 5.0Ap36



Wake up.  Fact is that there have been features which have been introduced
well over a year ago that still don't work.  There are a set of features
that commonly break in every second release.  Documentation for nearly
every release that I look at has obvious errors in version numbers,
content, etc.  These are things that I see in a quick glance over it, and
it isn't just once in a while but most of the time.

Ascend may be "forging ahead in areas of new technology", but the old
technology doesn't work.  

On Thu, 27 Nov 1997, Stephen Dolloff wrote:

> Garbage like this is really irritating.  What we have here is a company
> who is forging ahead in areas of new technology and communications.  They
> have consistantly continued to develop and support new and emerging
> features.  Not only do you want all of the new features yesterday, but you
> expect it to work perfectly and then on top of that, you have the gall to
> publicly criticize them for a one digit typo in documentation the day that
> it comes out.  Can you possibly tell me why this is necessary?  Or do you
> really have nothing better to do?
> 
> On Thu, 27 Nov 1997, Jaap Akkerhuis wrote:
> 
> > 
> >     The 5.0Ap36 (MAX 400x, 1800, 2000, 200+) has been given to support. This
> >     release contains the following corrections:
> >     
> > Interesting. The release notes talk about 5.0Ap34. Looks like another
> > fine example of Ascends quality control in action.
> > 
> > 	jaap
> > ++ Ascend Users Mailing List ++
> > To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
> > To get FAQ'd:	<http://www.nealis.net/ascend/faq>
> > 
> 
> ++ Ascend Users Mailing List ++
> To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd:	<http://www.nealis.net/ascend/faq>
> 

++ 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: