Downstream (software development)
 | This article is actively undergoing a major edit for a little while. To help avoid edit conflicts, please do not edit this page while this message is displayed. This page was last edited at 00:15, 14 May 2015 (UTC) (10 years ago) – this estimate is cached, . Please remove this template if this page hasn't been edited for a significant time. If you are the editor who added this template, please be sure to remove it or replace it with {{Under construction}} between editing sessions. |
In software development, downstream refers to a direction toward the original authors or maintainers of software that is distributed as source code, and is a qualification of either a bug or a patch. For example, a patch sent downstream is offered to the developers or maintainers of a forked software project. If accepted, the authors or maintainers will include the patch in their software, either immediately or in a future release. If rejected, the person who submitted the patch will have to maintain his or her own distribution of the author's software.
Upstream development allows other distributions to benefit from it when they pick up the future release.[1]
The term also pertains to bugs – responsibility for a bug is said to lie upstream when it is not caused through the distribution's porting and integration efforts.
See also
References
 | This computer-programming-related article is a stub. You can help Wikipedia by expanding it. |