Development workflow: Difference between revisions

Development workflow (view source)

257 bytes added , 13 May 2016

Temporary first version

329

edits

@@ Line 1: / Line 1: @@
-{{historical
+{{WIP}}
-| reason = The Gitorious open source infrastructure has been shut down and all of the FlightGear source code and data repositories migrated to SourceForge.
+{{Git}}
-| date   = February 2015
+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.
-}}
-This page outlines some ''first steps'' on how to do (code) development for [[FlightGear]].
+== 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=
@@ 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.]]
+-->
-[[Category:Core developer documentation]]