Downstream (software development)

In <a href="/facts/Software_development/UUfsAaYY">software development</a>, downstream refers to a direction away from the <a href="/facts/Software_engineering/KX6cE9kz">original authors</a> or <a href="/facts/Maintenance_mode/8oD1e3dk">maintainers</a> of software that is distributed as <a href="/facts/Source_code/o9J6Jv23">source code</a>, and is a qualification of a <a href="/facts/Patch_(Unix)/9tFn5GeU">patch</a>. For example, a patch sent downstream is offered to the developers or maintainers of a <a href="/facts/Fork_(software_development)/D6khxhpr">forked</a> software project. If accepted, the developers or maintainers will include the patch in their software fork, either immediately or in a future <a href="/facts/Software_release_life_cycle/z4Q4RElA">release</a>. Sometimes, "downstream" is used in contexts in which the developer does not have control, perhaps due to its inclusion as part other software or as part of a system.
For contrast, <a href="/facts/Upstream_(software_development)/5eKgNGAn">upstream</a> refers to code sent toward the original development team.

Downstream (software development) open-in-new

Downstream (software development)