Archive:Project fork: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{otheruses|fork (disambiguation)}} | {{otheruses|fork (disambiguation)}} | ||
In [[software engineering]], a '''project fork''' happens when developers take a copy of [[source code]] from one [[software package]] and start independent development on it, creating a distinct piece of software. [[free software|Free]] or [[open source]] software is inherently prone to forking. | |||
A kind of fork that is standard practice in many projects is a ''stable'' or ''release'' version, modified only for bug fixes, while a ''development'' tree develops new features. This is common practice in the [[Linux kernel]], for instance, but has been misrepresented occasionally in the trade press as the more problematic sort of fork described above.[http://www.groklaw.net/article.php?story=20041121124609671] Such forks are often referred to instead as "branches" both to avoid the negative connotations of a fork and because it is closer in intent and function to the common software engineering meaning of [[branching (software)|branching]]. | A kind of fork that is standard practice in many projects is a ''stable'' or ''release'' version, modified only for bug fixes, while a ''development'' tree develops new features. This is common practice in the [[Linux kernel]], for instance, but has been misrepresented occasionally in the trade press as the more problematic sort of fork described above.[http://www.groklaw.net/article.php?story=20041121124609671] Such forks are often referred to instead as "branches" both to avoid the negative connotations of a fork and because it is closer in intent and function to the common software engineering meaning of [[branching (software)|branching]]. | ||