-
Notifications
You must be signed in to change notification settings - Fork 0
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 |
| Result |
| name | Vote |
|---|---|
| Daniel | |
| Cayetano | |
| Regina | |
| Vicky | +1 (proposed by) |
| Rohith |
I am making this motion because a minor release would be done outside of the planned dates.
Mohamed Bakli 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 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 - get some feedback
-
On the meantime, add the functionality to other functions but in develop
- add the functionality of canceling the execution on all other functions (where applicable) - Make the release of 3.1.0
Maintained by the pgRouting Community
Website: https://pgrouting.org