Important things that should work / be there:

• tools refactoring (folders, tests)
• ballistic update
• set person variables via TraCI
• at least one additional car following model (IDM?) should pass all basic and spec tests
• marouter working
• working windows installer
• XML input format for OD-matrices (maybe derived from flows) and detector data
• XML schemata for all in- and output files
• default car following model reproduces lane usage statistics of A92 and A3 scenarios
• at least 2 pedestrian models available: ''ghost'' (current defautl, needs a better name, ''striping'' (simple colombo model, also needs a better name)
• Publication on the validity of the microsimulation model measured by a range of metrics and for a range of scenarios (in particular when using the default parameters)
• Documentation
  • document (and maybe fix) network format (junction vs. node?)
  • document (and maybe fix) vehicle input format for routers / sim (flow vs. trip vs. vehicle)
  • GUI documentation
  • consolidate the "specification" page with the rest of the documentation
  • resort other pages
  • generate a pdf/chm-book (include chm in Windows release) book deferred, no chm necessary
  • find and complete began but not finished pages (for example http://sumo.dlr.de/wiki/Demand/Dynamic_User_Assignment) deferred
  • add missing references to papers where appropriate (http://sumo.dlr.de/wiki/Demand/Dynamic_User_Assignment)
• import
  • check naming in imported Vissim networks (other as well)
  • close OpenDrive
  • documentation: clarify which versions are supported
• output
  • verify all detectors (is e2 over the whole lane generating same results as a lane-dump etc.) or document differences deferred
• GUI
  • view centers immediately
  • gui is responsive while loading (load thread) deferred
• nice-to-have
  • SUMO is capable of loading and closing a simulation completely via TraCI
• tools
  • consolidate methods and functions (determining where SUMO applications are located, see e.g. osmBuild)