Saltation (Software Engineering): Difference between revisions
wikademia>Stuartyeates No edit summary |
wikademia>Stuartyeates No edit summary |
||
| Line 1: | Line 1: | ||
{{wiki}} | {{wiki}} | ||
{{notable}} | {{notable}} | ||
Saltation is the exercise of updating a project's dependencies to the current published versions. | Saltation is the exercise of updating a project's dependencies to the current published versions. {{fact}} | ||
New versions of dependencies typically offer new features, deprecate and remove old features, fix bugs and change functionality. | New versions of dependencies typically offer new features, deprecate and remove old features, fix bugs and change functionality. | ||
Revision as of 00:29, 3 June 2009
Template:Wiki Template:Notable
Saltation is the exercise of updating a project's dependencies to the current published versions. [citation needed]
New versions of dependencies typically offer new features, deprecate and remove old features, fix bugs and change functionality.
Saltation is jerky and allows a period of time between code being changed and the effects of the change being noticed.
Saltation is the antithesis of Continuous Integration within which current snapshot builds of all dependencies are used.
