Jump to content

Talk:Upstream (software development)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Thumperward (talk | contribs) at 09:22, 22 December 2008 (moved Talk:Upstream (computer science) to Talk:Upstream (software development): splitting). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconComputing Stub‑class
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.
Note icon
This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the |auto= parameter.

IIRC, the terms upstream/downstream are also used for something i'd call the responsibility path in an open and separated software development process (i.e. the core developer group of a software project is in upstream direction from a distributer of the software). I'm not absolutely sure if this convention is common enough to go into wp. --85.72.38.226, 12:02, 20 Oct 2005 (UTC)

this was the definition i was looking for when i came to the page. 130.88.253.39 15:58, 2 February 2006 (UTC)[reply]
me too 142.59.153.99 04:45, 12 May 2006 (UTC)[reply]
It seems to me that this the term is used often enough to be relevant for inclusion which is why I took the liberty to add it. --Abraxa 13:35, 15 March 2007 (UTC)[reply]
The Jargon file has a useful entry - http://catb.org/~esr/jargon/html/U/upstream.html I am rewriting the software development section to also include this adjective as pertaining to bugs, which follow the same "responsibility path" (this term being too unfamiliar to mention, but "responsibility" generally filling a deficiency in the original entry. JeR (talk) 03:55, 25 March 2008 (UTC)[reply]


There is also a definition of upstream/downstream in RFC2616, which relates to the direction in which data is flowing for HTTP Chrisg67 14:04, 28 February 2007 (UTC)[reply]