2.1 Development Plan
As of March 23, 2015, we have collected a bunch of fixes and some features in the develop branch. We have just reviewed all the issues and have them tagged as 2.1.0 or 2.2.0 Milestones. Our goal, is to fix the remaining issues and try to a "quick"-ish release, but we still need to follow our basic process of testing, integration, documentation, beta and release candidates to insure a quality release and to minimize regressions against the 2.0 release.
- better argument type checking that appears to be implemented inconsistently across the code
- better consistency of results between the various algorithms, especially those using boost
- would like to improve or replace the basic VRP so that it optimizes the solution (time permitting)
- resolve the Milestone 2.1.0 issues where possible or push them to 2.2.0 if too risky
- updates to the cmake build system to better support postgresql version selection, creation of the sql files for installation and any updates that might be needed to support changes to the code
- The final focus for this release is 3 functions pgr_dijkstra, pgr_ksp, and pgr_drivingDistance as stated in pgRouting V2.1Towards V3.0.0
- pgr_dijkstra
- pgr_ksp
- pgr_drivingDistance
- issues milestoned for 2.1
- work on other issues or in other routing functions
- Tickets: https://github.com/pgRouting/pgrouting/milestones/Release%202.1.0
- Development branch: https://github.com/pgRouting/pgrouting/tree/develop
- PostGIS Coding Styles: http://trac.osgeo.org/postgis/wiki/DevWikiMain
- Non for the moment
