Greg, it all depends on how much re-factoring is done in a "patch". There's nothing to prevent a "patch" from replacing entire packages with entirely new packages. In VistA, we've stretched the definition of "patch" to no longer be anything at all like a traditional patch.
The "case now" all depends on what gets approved by management. Make the case and it will be done. There are two reasons that "patches" are used so extensively over releasing "new versions". 1. The perceived notion by management that "new versions" require much more documentation overhead than "patches". 2. The accurate recognition that "patches" in VistA are easier to distribute than "new versions" due to the semi-automated process of configuration management and release management. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Woodhouse Sent: Tuesday, October 11, 2005 3:11 PM To: [email protected] Subject: Re: [Hardhats-members] Wish list? --- Nancy Anthracite <[EMAIL PROTECTED]> wrote: > OK, Greg, as soon as we get this wishlist done, we maybe can start on > > redesigning the whole system architecture. I think that might better > fit > your wish list. ;-) > > And VOE DOES exist and those enhancements WILL happen. Have faith! > "Everything comes to he who waits." > > Who said that anyway? I haven't seen that in your lists of quotes. > It would be interesting if it were possible to run a controlled experiment: In one group, VistA would be reworked as needed, even if entire applications were rewritten from scratch. In the second group, a process of incremental "patching" would be followed (much as is the case now). I would conjecture that over a suitable horizon (say 10 years) the first group would end up spending *less* on software development, maintenance and support than the second group spends on support and maintenance. === Gregory Woodhouse <[EMAIL PROTECTED]> "Einstein was a giant. He had his head in the clouds and his feet on the ground." -- Richard P. Feynman ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
