Editing Patch (computing) (section)

== Variants ==

=== Hotfix ===
{{Main|Hotfix}}
A hotfix or Quick Fix Engineering update (QFE update) is a single, cumulative package that includes information (often in the form of one or more files) that is used to address a problem in a software product (i.e., a software bug). Typically, hotfixes are made to address a specific customer situation. [[Microsoft]] once used this term but has stopped in favor of new terminology: General Distribution Release (GDR)  and Limited Distribution Release (LDR). [[Blizzard Entertainment]], however, defines a hotfix as "a change made to the game deemed critical enough that it cannot be held off until a regular content patch".

=== Point release ===
{{Main|Point release}}
A point release is a [[minor release]] of a software project, especially one intended to fix bugs or do small cleanups rather than add significant [[Feature (software design)|features]]. Often, there are too many bugs to be fixed in a single major or minor release, creating a need for a point release.

=== Program temporary fix ===
{{Main|Program temporary fix}}
Program temporary fix or Product temporary fix (PTF), depending on date, is the standard [[IBM]] terminology for a single bug fix, or group of fixes, distributed in a form ready to install for customers. A PTF was sometimes referred to as a “ZAP”.<ref>{{Cite web|url=https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zdatamgmt/zsysprogc_utilities_SPZAP.htm|title=SPZAP (a.k.a. Superzap): Dynamically update programs or data|website=IBM Knowledge Center|language=en-US|access-date=2020-02-23|archive-date=2020-05-24|archive-url=https://web.archive.org/web/20200524134045/https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zdatamgmt/zsysprogc_utilities_SPZAP.htm|url-status=live}}</ref>
Customers sometime explain the acronym in a tongue-in-cheek manner as ''permanent temporary fix'' or more practically ''probably this fixes'', because they have the option to make the PTF a permanent part of the operating system if the patch fixes the problem.

=== {{Anchor|SECURITY}}Security patches ===
A ''security patch'' is a change applied to an asset to correct the weakness described by a vulnerability. This corrective action will prevent successful exploitation and remove or mitigate a threat's capability to exploit a specific vulnerability in an asset. Patch management is a part of [[vulnerability management]]{{snd}} the cyclical practice of identifying, classifying, remediating, and mitigating vulnerabilities.

Security patches are the primary method of fixing security vulnerabilities in software. Currently Microsoft releases its security patches once a month ("[[patch Tuesday]]"), and other operating systems and software projects have security teams dedicated to releasing the most reliable software patches as soon after a vulnerability announcement as possible. Security patches are closely tied to [[responsible disclosure]].

These security patches are critical to ensure that business process does not get affected. In 2017, companies were struck by a ransomware called [[WannaCry ransomware attack|WannaCry]] which encrypts files in certain versions of [[Microsoft Windows]] and demands a ransom via BitCoin. In response to this, Microsoft released a patch which stops the ransomware from running.

=== Service pack ===
{{Main|Service pack}}
A service pack or SP or a feature pack (FP) comprises a collection of updates, fixes, or enhancements to a software program delivered in the form of a single installable package. Companies often release a service pack when the number of individual patches to a given program reaches a certain (arbitrary) limit, or the software release has shown to be stabilized with a limited number of remaining issues based on users' feedback and bug tracking such as [[Bugzilla]]. In large software applications such as office suites, operating systems, database software, or network management, it is not uncommon to have a service pack issued within the first year or two of a product's release. Installing a service pack is easier and less error-prone than installing many individual patches, even more so when updating multiple computers over a network, where service packs are common.

=== Unofficial patches ===
{{Main|Unofficial patch}}
An unofficial patch is a patch for a program written by a third party instead of the original [[Software developer|developer]]. Similar to an ordinary patch, it alleviates [[Software bug|bugs]] or shortcomings. Examples are security fixes by security specialists when an official patch by the software producers itself takes too long.<ref name="hsecurity2007">{{cite web |url=http://www.h-online.com/security/news/item/Unofficial-patch-for-Windows-URI-problem-733796.html |date=2007-10-16 |title=Unofficial patch for Windows URI problem |publisher=The H Security |first=Mike |last=Barwise |access-date=2012-01-29 |archive-date=2021-04-29 |archive-url=https://web.archive.org/web/20210429103610/http://www.h-online.com/security/news/item/Unofficial-patch-for-Windows-URI-problem-733796.html |url-status=live }}</ref><ref>{{cite web |url=http://www.computerweekly.com/news/2240077005/Another-unofficial-IE-patch-offered-to-counter-critical-flaw |title=Another unofficial IE patch offered to counter critical flaw |date=2006-03-30 |quote=''Another unofficial patch has been released to counter a critical flaw in Microsoft's Internet Explorer browser.'' |publisher=[[Computer Weekly]] |access-date=2013-07-09 |archive-date=2021-05-02 |archive-url=https://web.archive.org/web/20210502174020/https://www.computerweekly.com/news/2240077005/Another-unofficial-IE-patch-offered-to-counter-critical-flaw |url-status=live }}</ref> Other examples are unofficial patches created by the [[game community]] of a [[video game]] which became unsupported.<ref name="mythalive2004">{{cite web |url=http://linuxdevcenter.com/pub/a/linux/2004/06/10/mythdevelopers.html |title=Keeping the Myths Alive |first=Howard |last=Wen |date=2004-06-10 |access-date=2012-12-22 |publisher=linuxdevcenter.com |quote=''[...]fans of the Myth trilogy have taken this idea a step further: they have official access to the source code for the Myth games. Organized under the name MythDevelopers, this all-volunteer group of programmers, artists, and other talented people devote their time to improving and supporting further development of the Myth game series.'' |archive-date=2013-04-06 |archive-url=https://web.archive.org/web/20130406161344/http://www.linuxdevcenter.com/pub/a/linux/2004/06/10/mythdevelopers.html |url-status=live }}</ref><ref name="timcalltopower2">{{cite web|url=http://timreview.ca/article/294 |title=Opening the Source of Art |date=2009-10-01 |first=John |last=Bell |quote=''[...]that no further patches to the title would be forthcoming. The community was predictably upset. Instead of giving up on the game, users decided that if Activision wasn't going to fix the bugs, they would. They wanted to save the game by getting Activision to open the source so it could be kept alive beyond the point where Activision lost interest. With some help from members of the development team that were active on fan forums, they were eventually able to convince Activision to release Call to Power II's source code in October of 2003.'' |publisher=Technology Innovation Management Review |access-date=2012-12-30 |url-status=dead |archive-url=https://web.archive.org/web/20140330084636/http://timreview.ca/article/294 |archive-date=2014-03-30 }}</ref>

=== Monkey patches ===
{{Main|Monkey patch}}

[[Monkey patch]]ing means extending or modifying a program locally (affecting only the running instance of the program).