Difference between revisions of "Antipodes Commit Checklist"

From FreeSpace Wiki
Jump to: navigation, search
(I am yet to retest Antipodes 5 Redux on Xcode 2.5/ OS X 10.4)
(Updated for Antipodes 5 Redux results on Xcode 2.5 / OS X 1.4 PPC)
Line 4: Line 4:
 
** <span style="color:green;">VS2008 (almost any SCP member/Zacam)</span>
 
** <span style="color:green;">VS2008 (almost any SCP member/Zacam)</span>
 
** VC6 (Goober5000, chief1983)
 
** VC6 (Goober5000, chief1983)
** Xcode 2.5 (Echelon9)
+
** <span style="color:green;">Xcode 2.5 (Echelon9)</span>
 
** <span style="color:green;">Xcode 3.2.1 (chief1983, Echelon9)</span>
 
** <span style="color:green;">Xcode 3.2.1 (chief1983, Echelon9)</span>
 
** <span style="color:green;">Linux with GCC 4.x (chief1983)</span>
 
** <span style="color:green;">Linux with GCC 4.x (chief1983)</span>
Line 11: Line 11:
 
** Windows Vista ()
 
** Windows Vista ()
 
** <span style="color:green;">Windows 7 (chief1983/Zacam)</span>
 
** <span style="color:green;">Windows 7 (chief1983/Zacam)</span>
** OS X 10.4 (Echelon9)
+
** <span style="color:green;">OS X 10.4 (Echelon9)</span>
 
** OS X 10.5 PPC ()
 
** OS X 10.5 PPC ()
 
** OS X 10.5 Intel ()
 
** OS X 10.5 Intel ()

Revision as of 17:06, 20 January 2010

This is a list of things to check before moving code from the Antipodes branch to Trunk, and who is in charge or capable of signing off on each item. We should have at least two members responsible for every task.

  • Verify that building succeeds on the following platforms (Release Engineering):
    • VS2008 (almost any SCP member/Zacam)
    • VC6 (Goober5000, chief1983)
    • Xcode 2.5 (Echelon9)
    • Xcode 3.2.1 (chief1983, Echelon9)
    • Linux with GCC 4.x (chief1983)
  • Verify builds run on the following, and interoperate properly with their respective launchers (HLP Bughunters):
    • Windows XP (Zacam)
    • Windows Vista ()
    • Windows 7 (chief1983/Zacam)
    • OS X 10.4 (Echelon9)
    • OS X 10.5 PPC ()
    • OS X 10.5 Intel ()
    • OS X 10.6 (chief1983, Echelon9)
    • Linux ()
  • Verify standalone server functionality (FUBAR and MULTI)
  • Verify on Windows that FRED runs, loads, check some dialogs, and saves ()

This is in addition to any other testing specific to the changes being made, that should already be done. This is mostly to catch common oversights when a coder is focusing on one platform and may neglect others in the process.