Proposal is to put in an End-Of-Life and Versioning policy for pgRouting similar to PostGIS and pgRouting:
https://postgis.net/eol_policy/
https://www.postgresql.org/support/versioning/
This will make it clear to users and packagers which versions we support and when they should be stop supporting versions. This is particularly important for security conscious orgs who are required to not run with software that has vulnerabilities.
Any software that has reached End-Of-Life, will not have any security patches applied to it and unless an org is willing to pay for the extra labor for us to back-port a fix, we will not do it.
Proposal is to put in an End-Of-Life and Versioning policy for pgRouting similar to PostGIS and pgRouting:
https://postgis.net/eol_policy/
https://www.postgresql.org/support/versioning/
This will make it clear to users and packagers which versions we support and when they should be stop supporting versions. This is particularly important for security conscious orgs who are required to not run with software that has vulnerabilities.
Any software that has reached End-Of-Life, will not have any security patches applied to it and unless an org is willing to pay for the extra labor for us to back-port a fix, we will not do it.