Development workflow: Difference between revisions
Jump to navigation
Jump to search
m (Elgaton moved page Development Workflow to Development workflow: Style page case according to FGW:MOS) |
(Temporary first version) |
||
| Line 1: | Line 1: | ||
{{ | {{WIP}} | ||
{{Git}} | |||
This page is meant to be a high-level introduction to the '''development workflow''' of FlightGear, that is, the process developers follow to contribute their work to the project. | |||
== The big picture == | |||
- Code, mailing lists, bug tracker hosted at SourceForge | |||
- Commit access: repos not public (see policy) | |||
== Life of a patch == | |||
- get the repo + fork | |||
- edit (on main for aircraft, on branch for | |||
- get feedback for important edits | |||
- submit a patch (or direct commit if commit access) | |||
- patch applied | |||
- check build server and monitor forum+ML | |||
== Tips == | |||
Ask on ML | |||
<!-- | |||
=The Big Picture= | =The Big Picture= | ||
| Line 29: | Line 43: | ||
[[File:Gitorious_cloning_button.png|thumb|400px|The '''Clone repository''' button on <nowiki>https://gitorious.org/fg</nowiki> copies (clones) a Gitorious repository into ones private Gitorious account.]] | [[File:Gitorious_cloning_button.png|thumb|400px|The '''Clone repository''' button on <nowiki>https://gitorious.org/fg</nowiki> copies (clones) a Gitorious repository into ones private Gitorious account.]] | ||
--> | |||
Revision as of 23:15, 13 May 2016
 |
Work in progress This article or section will be worked on in the upcoming hours or days. See history for the latest developments. |
| Git |
|---|
|
Git is a version control system, used to store all files required to build FlightGear. |
This page is meant to be a high-level introduction to the development workflow of FlightGear, that is, the process developers follow to contribute their work to the project.
The big picture
- Code, mailing lists, bug tracker hosted at SourceForge - Commit access: repos not public (see policy)
Life of a patch
- get the repo + fork - edit (on main for aircraft, on branch for - get feedback for important edits - submit a patch (or direct commit if commit access) - patch applied - check build server and monitor forum+ML
Tips
Ask on ML