Saltation (Software Engineering): Difference between revisions
Appearance
wikademia>Timp21337 Initial version |
wikademia>Stuartyeates No edit summary |
||
| Line 1: | Line 1: | ||
{{fact}} | |||
{{wiki}} | |||
{{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. | ||
| Line 6: | Line 10: | ||
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. | ||
{{stub}} | |||
Revision as of 00:29, 3 June 2009
[citation needed] Template:Wiki Template:Notable
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.
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.
