3 ms·
always updated ... which is well-intended, but it scares me if that means that all of my installations have version updates at the same time without manual int
by DrScump 10y ago
always updated
... which is well-intended, but it scares me if that means that all of my installations have version updates at the same time without manual intervention or advance notification. What if there's a defect or an introduced fail in backward compatibility? I'd be dead in the water.
Can you designate phased updates such that managers/leads are updated first, followed by staged updates for the remainder (with manual on-demand update available, of course)?
In my experience, there is too little attention given to backward compatibility. Even we as customers are using a feature "incorrectly", it's still a problem if your legacy code base (or applications and documents, in the Office example) is broken by an unexpected update.
- nolok 10y agoThe last update, I was warned that an update would be rolled out to my users before it started. I don't remember how long of a delay I had, I am certain I could not schedule it to a time of my choosing BUT I could force it to happen right now on a user by user basis. Which is what we ended up doing so as to control our update time. As for the backward compatibility, I agree in general but disagree about office, or particularly about word and excel. Its support for legacy stuff is insane, and a large part of why companies with lot of legacy stuff aren't moving to another solution anytime soon.