On 06/09/2012 15:44, Sam Heard wrote: > Hi Tom > > I absolutely agree with your summary. Technically I think making use > of obsolescence is the appropriate way to go in software. No competent > vendor will put out an operating system, compiler or software that > breaks existing tools without doing the work for them. > > The point I am making is that there are now health records out there > so we need to be absolutely clear that existing health records will > work with changes. If we want to use upgrade scripts these need to be > handled between releases so that the old and new work at the same time > for a while and ensure we have planned obsolescence over a period of > software cycles (say 3-5 years).* > *
yep. That's called release management ;-) - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120906/eeebe0c1/attachment.html>
