Release plan: Difference between revisions

Release plan (view source)

Revision as of 16:54, 23 August 2012

62 bytes added , 23 August 2012

→‎Definition of repository states: align images and text in a table

Gijs

Bureaucrats, checkuser, Interface administrators, Administrators

8,564

edits

@@ Line 81: / Line 81: @@
 === Definition of repository states ===
-* [[File:Traffic light green.png|27px]] Open/Green
+{| class="wikitable"
-*:Normal development of the code base and fgdata. Unrestricted (well, sort of) access to the streams. This state lasts for five month after the release branches were created.
+!
-* [[File:Traffic light yellow.png|27px]] Frozen/Yellow
+! State
-*:No new features or major changes shall be pushed onto the development streams (neither source nor data). This period is for preparing the code for the release and make sure there are no major issues. It lasts for four weeks until creation of the release branches.
+! Description
-*:It's a good idea for aircraft developers to adhere to this rule. However, aircraft in FGDATA may be handled as an exception from the frozen state. Any change to aircraft may be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Also, aircraft defined as part of the base package (e.g. the c172p) enter the frozen state and shall not undergo major changes in that period.
+|-
-* [[File:Traffic light red.png|27px]] Closed/Red
+! [[File:Traffic light green.png|20px]]
-*:Nothing shall be pushed to the development streams (simgear, flightgear and fgdata). This state is for creating the release branches. It lasts for just a few hours on Jan 17th and Jul 17th around 12:00 UTC.
+! Open/Green
+| Normal development of the code base and fgdata. Unrestricted (well, sort of) access to the streams. This state lasts for five month after the release branches were created.
+|-
+! [[File:Traffic light yellow.png|20px]]
+! Frozen/Yellow
+| No new features or major changes shall be pushed onto the development streams (neither source nor data). This period is for preparing the code for the release and make sure there are no major issues. It lasts for four weeks until creation of the release branches.
+It's a good idea for aircraft developers to adhere to this rule. However, aircraft in fgdata may be handled as an exception from the frozen state. Any change to aircraft may be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Also, aircraft defined as part of the base package (e.g. the c172p) enter the frozen state and shall not undergo major changes in that period.
+|-
+! [[File:Traffic light red.png|20px]]
+! Closed/Red
+| Nothing shall be pushed to the development streams (simgear, flightgear and fgdata). This state is for creating the release branches. It lasts for just a few hours on Jan 17th and Jul 17th around 12:00 UTC.
+|}
 === Bug fix committing policy ===