Saltation (Software Engineering): Difference between revisions

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.

@@ Line 1: / Line 1: @@
-{{dated prod|concern = non-notable neologism|month = June|day = 3|year = 2009|time = 08:52|timestamp = 20090603085218}}
-<!-- Do not use the "dated prod" template directly; the above line is generated by "subst:prod|reason" -->
-{{Wikify|date=June 2009}}
-{{Notability|date=June 2009}}
 Saltation is the exercise  of updating a project's dependencies to the current published versions. {{Fact|date=June 2009}}
@@ Line 11: / Line 6: @@
 Saltation is the antithesis of [[Continuous Integration]] within which current snapshot builds of all dependencies are used.
-{{stub}}