Saltation (Software Engineering): Difference between revisions
wikademia>Stuartyeates No edit summary |
wikademia>Wikademia No edit summary |
||
| (4 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
Saltation is the exercise of updating a project's dependencies to the current published versions. {{Fact|date=June 2009}} | |||
Saltation is the exercise of updating a project's dependencies to the current published versions. {{ | |||
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. | ||
| Line 10: | Line 6: | ||
Saltation is the antithesis of [[Continuous Integration]] within which current snapshot builds of all dependencies are used. | Saltation is the antithesis of [[Continuous Integration]] within which current snapshot builds of all dependencies are used. | ||
Latest revision as of 05:35, 13 June 2009
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.