| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 252.1 | I might know soon. | HEWIE::RUSSELL | BX Turbo drivers do it with woooosh! | Tue Jun 20 1989 15:51 | 11 |
| Jane,
I'm expecting the "offical" layered product list for VMS V5.1 "real soon
now".
I'll send it to the EASE: distribution list as well as posting it here.
If CMS V3.1 is on the list, then you can expect it (along with VMS V5.1)
on FUTURS sometime around "mid-July-ish".
Peter.
|
| 252.2 | it's on CURRNT... | SHAPES::ALFORDJ | Dragon Riders do it in between... | Tue Jun 20 1989 17:56 | 10 |
| > I'll send it to the EASE: distribution list as well as posting it here.
> If CMS V3.1 is on the list, then you can expect it (along with VMS V5.1)
I don't know about the list, but when I installed V3.0 on a microVax I got
a mail back (Jerry knows about it) saying something in the order of -
Lots of bugs have been found in V3.0 so that release has been effectively
cancelled. Install V3.1 instead.
Talk to Jerry, he may need reminding....
|
| 252.3 | Ooooops | SHAPES::ALFORDJ | Dragon Riders do it in between... | Tue Jun 20 1989 17:58 | 4 |
|
Sorry, it's V3.2 on CURRNT !
I thought FUTURS was supposed to be "futures" cluster :-)
|
| 252.4 | CMS V3.2 ON FUTURS
| CUCKOO::THOMPSON | | Wed Jun 21 1989 13:26 | 12 |
| EASE V5.0-2 included a CMS V3.0 kit, complete with bugs. So the 2 EASE'd
clusters have had CMS v3.2 installed. It would therefore seem logical that
we install CMS v3.2 on FUTURS as soon as possible to avoid messing up
CMS libraries that might be moved between clusters.
The only potential problem I can think of is if a product is shipped to a
production site and tries to use the EASE version (CMS v3.0) then it may
fall over because it was built using v3.2 .
However I don't know of any product that relies on
CMS to do its job. So unless anyone objects CMS V3.2 will be installed
on FUTURS on Friday 23rd June.
|