Aircraft testing checklist: Difference between revisions

If we do this, it’s easier make some ticket searches to see what aircraft have open issues, and which aircraft are abandoned.

 

If the aircraft has an obvious active maintainer, it would be excellent to point them at the ticket

* we’re not so interested in issues ’smaller’ than the ones on this list, broadly. If the fuel cap is in the wrong place for the 1972 model of the Piper Archer, that’s something to take up with the aircraft maintainer or learn how to fix yourself :) This is about getting a decent number of aircraft verified as being in a useful/flyable state, not about collecting a huge amount of trivial defects which will never get fixed.  

* The list is not exhaustive: if the Harrier can’t take off vertically, or a water-bomber can’t pick up water, those are ‘big’ issues for that aircraft, despite not being on the testing list.

* for aircraft which are actively under development / maintained, someone still can test them, but apply common sense, Eg if you know the F-15 or A320 is developed in an upstream repository, probably just file any issues in the tracker for that aircraft repo (if it exists), no need to waste people’s time duplicating them into the SF Tracker.  

* If you encounter an issue which you suspect is generic to all of FlightGear, report it as normal in the tracker, or ask about it here - don’t bury it in the aircraft testing report.