Difference between revisions of "Antipodes Commit Checklist"

From FreeSpace Wiki
Jump to: navigation, search
(Updates to testing targets)
(Tweak the OS X target range)
 
Line 12: Line 12:
 
** Windows 8.1 (community)
 
** Windows 8.1 (community)
 
** Windows 10 (chief1983, community)
 
** Windows 10 (chief1983, community)
** OS X 10.8, 10.9, 10.10, 10.11, maybe more (chief1983, Echelon9, community)</span>
+
** OS X 10.7 - 10.11 (chief1983, Echelon9, community)</span>
 
** Linux (Ubuntu latest and current LTS, Debian, FC) (community)
 
** Linux (Ubuntu latest and current LTS, Debian, FC) (community)
 
** FreeBSD 10.2 (community)
 
** FreeBSD 10.2 (community)

Latest revision as of 16:14, 26 January 2016

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):
    • VS2010, VS2012 and VS2015 (done automatically by AppVeyor [1])
    • gcc 4.6.3 (Linux) and Apple LLVM 6 (MacOS) (done automatically by Travis CI [2])
    • Xcode 6.4 (chief1983)
    • Xcode 7.2 (?)
    • clang 3.4.1 (FreeBSD 10.2) (chief1983)
  • Verify builds run on the following, and interoperate properly with their respective launchers (HLP Bughunters):
    • Windows XP (Zacam)
    • Windows 7 (chief1983/Zacam)
    • Windows 8.1 (community)
    • Windows 10 (chief1983, community)
    • OS X 10.7 - 10.11 (chief1983, Echelon9, community)
    • Linux (Ubuntu latest and current LTS, Debian, FC) (community)
    • FreeBSD 10.2 (community)
  • Verify standalone server functionality (chief1983)
  • Verify on Windows that FRED runs, loads, check some dialogs, and saves (community)

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.