Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!UWOCC1.BITNET!A105 From: A105@UWOCC1.BITNET (Brent Sterner) Newsgroups: mod.computers.vax Subject: s/w upgrades in mid-term (edu site) Message-ID: <8609021618.AA01292@ucbvax.Berkeley.EDU> Date: Tue, 2-Sep-86 11:08:00 EDT Article-I.D.: ucbvax.8609021618.AA01292 Posted: Tue Sep 2 11:08:00 1986 Date-Received: Tue, 2-Sep-86 21:18:11 EDT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 17 Approved: info-vax@sri-kl.arpa This is for edu sites. It is customary here to batch our s/w upgrades at the end of term. For VMS, is this really necessary? The reason I ask is that we have 6 DEC languages, and the volume by term-end can be fairly large. We also have some non-DEC products to be considered. Do any of your sites attempt any upgrades in mid-term? This mostly applies to maintenance releases. I'd never upgrade VMS to say 4.4 except in a slow period. Am I being too cautious here as well? Brent Sterner Computing & Communications Services Natural Sciences Building The University of Western Ontario London, Ontario, Canada N6A 5B7 Telephone (519)661-2151 x6036 Network