MOTION 1: Speed up Release 3.1.0

Concept	value
Number	MOTION 1
Date of motion	June 1
Title	Speed up Release 3.1.0
Mail Thread	pgRouting-dev
Result	Pass

name	Vote
Daniel	+1
Cayetano	+1
Regina	+1
Vicky	+1 (proposed by)
Rohith	No vote

Mail thread for comments

I am making this motion because a minor release would be done outside of the planned dates.

Mohamed Bakli From MobilityDB found a solution to have pgRouting execution to be stopped for example when running from psql using the code executes the interruption and nothing is returned. The related issue

https://github.com/pgRouting/pgrouting/issues/232

This is how it would be implemented:

• https://github.com/mahmsakr/pgrouting/blob/b9d12a5047104ee3e9271d01879277fd71d01d64/include/dijkstra/pgr_dijkstra.hpp#L57
• https://github.com/mahmsakr/pgrouting/blob/b9d12a5047104ee3e9271d01879277fd71d01d64/include/dijkstra/pgr_dijkstra.hpp#L329

As we all know, pgRouting has 2 main branches, currently

• master we will be for working the next micro: 3.0.1
• develop we will be for working the next mini: 3.1.0

This functionality is very important, so I think it is good to have a next 3.0.1 release ASAP

In order to have the functionality tested by a broad number of users:

• Add it only to the pgr_dijkstra function on Master
  • Will cherry pick the commit and move to develop
  • Make the release of 3.0.1 only with pgr_dijkstra function using that functionality (one commit)
  • get some feedback
• On the meantime, add the functionality to other functions in master
  • add the functionality of canceling the execution on all other functions (where applicable)
  • Make the release of 3.0.2 (one commit)
  • Will cherry pick the commit and move to develop

The MobilityDB team is using pgRouting (and PostGIS) and started communication with us: mail1 mail2

And the results of this communication is this PR into develop.

For their current development of the open source of MobilityDB they need the functionality. Corresponding pgtap tests and documentation was also added.

So for the sake of continuous development of both open source project (pgRouting & MobilityDB) I am proposing the following timeline:

• Release of 3.0.1 once the PR of 1 commit (cherry pick to develop)
• Release of 3.0.2 once the PR of 1 commit (cherry pick to develop)
• Release of 3.1.0 once the PR of 1 commit (This is a minor and would add a new signature function overloading pgr_dijkstra, as proposed and will not affect the current functions)