That's really the responsibility of the area being changed, not KIDS. Kind of like the captain of the ship evacuating all but the most essential personnel before the pumps are turned on. The captain (in VistA it would be the developer responsible for the environment checks and pre-installation checks) know who can stay and who shouldn't. BTW, environment checks are to make NO changes other than the presence of the routine(s) to do the checks. Pre-install code is permitted to make changes prior to the loading of new components. (These are enforced by policy and careful SQA review ... KIDS can't "know" what's really going to happen.)
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of K.S. Bhaskar Sent: Monday, August 29, 2005 2:09 PM To: [email protected] Subject: RE: [Hardhats-members] Re: GT.M and user/memory/object code space Cool! I didn't know KIDS did all that. So what we now need is to establish the set of signals that tell a ship that it needs to go into dry dock for an oil change (or whatever ships do in floating dry docks when on maneuvers - excuse my skimpy nautical knowledge). What does KIDS do if a process is in an area that it wants to change? -- Bhaskar On Mon, 2005-08-29 at 15:54 -0500, Cameron Schlehuber wrote: > All patches and version updates to VistA in VA are handled via KIDS > (or at > least they're supposed to!) One of the capabilities KIDS offers is to > lock > out users of selected options related to the code being changed. > Other > users then can continue their merry way during what in some cases may > be > lengthy installation processes. Rather than VistA being like a car > (a > system), it's more like a fleet (a system of systems), where we even > have > the equivalent of floating dry-docks to do repairs while engaged in > active > maneuvers. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
