![]() However, with no stability in the feature list or functionality, this affects the ability for documentation, other software that interfaces with the software, plugins, and more to function: a change in the software can mean these become out of date or fail to work anymore. In many cases, these releases also fix deficiencies or bugs that would otherwise remain stagnant in the stable release. Some people like that with non-stable releases such as development snapshots, beta releases or rolling releases, they are always getting the latest features as soon as they are written into the software. You cannot depend on them to behave the same way from one week to the next. A characteristic of all three of these is that they are in a frequent state of change even their functionality and feature list can change from week to week, or day to day. Any problems with the software (unless they can easily be fixed with a bug fix update) are “known” problems, and the software vendor does not need to keep track of more than one variantion of these problems for any given version.Įxamples of releases that are the opposite of stable include development snapshots, beta releases, and rolling releases. To get new functionality users eventually need to upgrade to the next version. It is released, and following the release no new features are added apart from the odd bug fix. Software that is intended for the public to use is usually “stable”. Apart from security patches and bug fixes, the software will not change for as long as that version of the software is supported, usually from 1 to many years. Its behaviour, functionality, specification or API is considered ‘final’ for that version. ![]() I’ve come to learn that when someone refers to software as ‘stable’, there is more than one quite different thing they might mean.Ī stable software release is so named because it is unchanging. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |