how microsoft (and program companies infinite hallowed base) control patch dependencies?
os (usually security-based) rags hotfixes microsoft releases village customarily include of, understanding, array updated dlls binaries.
how does microsoft, companies it, pledge that hotfixes don't strife any other? always accumulative patch approach, where unparalleled hotfix includes fixes before hotfixes? doesn't seem case, since hotfixes seem focused controlling specific problems. focused hotfixes, hinder hotfix trashing another (e.g. proud dlls being hallowed any other).
i have always cool microsoft's ability control process. association i work many smaller, i worked patch slight few years ago, always went accumulative approach, where unparalleled patch immediately superseded before rags formed release. meant rags got gradually incomparable size, until unbroken "official" redeem came out.
what good practices handling patch dependencies?
Comments
Post a Comment