A maintenance release (also minor release or Maintenance Pack or MP) is a release of a product that does not add new features or content. For instance, in computer software, maintenance releases are typically intended to solve minor problems, typically "bugs" or security issues.
Example of minor version numberingedit
The somewhat unusual version number "3.0.5a" was used for a minor release of KDE because of a lack of version numbers. Work on KDE 3.1 had already started and, up to that day, the release coordinator used version numbers such as 3.0.5, 3.0.6 internally in the main CVS repository to mark snapshots of the upcoming 3.1. Then after 3.0.3, a number of important and unexpected bug fixes (starting from 3.0.4) suddenly became necessary, leading to a conflict, because 3.0.5 was at this time already in use. More recent KDE release cycles have tagged pre-release snapshots with large revision numbers, such as 3.1.95, to avoid such conflicts.
maintenance, release, this, article, does, cite, sources, please, help, improve, this, article, adding, citations, reliable, sources, unsourced, material, challenged, removed, find, sources, news, newspapers, books, scholar, jstor, december, 2009, learn, when,. This article does not cite any sources Please help improve this article by adding citations to reliable sources Unsourced material may be challenged and removed Find sources Maintenance release news newspapers books scholar JSTOR December 2009 Learn how and when to remove this message A maintenance release also minor release or Maintenance Pack or MP is a release of a product that does not add new features or content For instance in computer software maintenance releases are typically intended to solve minor problems typically bugs or security issues Example of minor version numbering editThe somewhat unusual version number 3 0 5a was used for a minor release of KDE because of a lack of version numbers Work on KDE 3 1 had already started and up to that day the release coordinator used version numbers such as 3 0 5 3 0 6 internally in the main CVS repository to mark snapshots of the upcoming 3 1 Then after 3 0 3 a number of important and unexpected bug fixes starting from 3 0 4 suddenly became necessary leading to a conflict because 3 0 5 was at this time already in use More recent KDE release cycles have tagged pre release snapshots with large revision numbers such as 3 1 95 to avoid such conflicts See also editPatch computing Software versioning Software release life cycle Point release nbsp This software engineering related article is a stub You can help Wikipedia by expanding it vte Retrieved from https en wikipedia org w index php title Maintenance release amp oldid 954954286, wikipedia, wiki, book, books, library,
