🚀 go-pugleaf

Allen B writes
> 
> Considering our semester starts on the 24th, the 3.0
> release is really too late for me whenever it is.  I got  
the
> impression from early news of 3.0 that I'd have it up and
> running by now.  The date kept slipping and so did my  
chance
> of using it any time soon.  
> 
> A big "Boo!  Hiss!" to missing a summer release date.  I  
now
> either have to close our lab or wait 'til October to get  
the
> job done right.  I'm sure other Universities have similar
> situations. 
> 
> If NeXT is still aiming at higher education, they're not
> hitting it very well.  Our machines should be stable and
> consistent all semester long.  Making me do an upgrade
> once a semester is underway is not a way to be my friend. 
> 
> I'm not opposed to coming in weekends and working late
> nights to get machines upgraded and tested.  I'd just
> rather do it between sessions and not when 440 users are
> expecting to use our 24 hour lab.   
> 
> Allen B (Not the best NeXTperson to piss off)

(Perhaps the next-best person to....)

I know that Next has been working hard to make sure this  
release is bug-free software (oxymoron?) but having watched  
numerous VMS, AIX, Ultrix, DOS (Ugh) Windows (Ugh  
factorial) come down the pipe, let me say this:  Don't  
commit too deeply.

Were I in Allen's shoes I'd upgrade 1 machine in each lab  
to 3.0, and wait and see what happens.


On the flip side, I too am eagerly awaiting the release.   
But it will b installed on only 1 machine for two months  
before I consider putting it on the rest.