Downstream (software development)

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) This article appears to be a dictionary definition. Please help expand it to present the subject encyclopedically. (May 2023) (Learn how and when to remove this message) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Downstream" software development – news · newspapers · books · scholar · JSTOR (January 2025) (Learn how and when to remove this message) (Learn how and when to remove this message)

In software development, downstream refers to a direction away from the original authors or maintainers of software that is distributed as source code, and is a qualification of a patch. For example, a patch sent downstream is offered to the developers or maintainers of a forked software project. If accepted, the developers or maintainers will include the patch in their software fork, either immediately or in a future release. 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.^[1]

For contrast, upstream refers to code sent toward the original development team.

1. ^ Wolf, Marty; Miller, Keith; Grodzinsky, Frances (2019-05-28). "On the Responsibility for Uses of Downstream Software". Computer Ethics - Philosophical Enquiry (CEPE) Proceedings. 2019 (1). doi:10.25884/7576-wd27. ISSN 2689-2782.

This computer-programming-related article is a stub. You can help Wikipedia by expanding it.

• v
• t
• e