If anyone is interested in speeding up support for Varnish 6.1 and 6.2 (and why not the master branch too) we first need to remove all the bits and pieces in the source tree that enables support for 4.x and 5.x releases.
This is not hard if you are familiar with the Varnish code base, but it's tedious.
Once we are free of all those conditional code paths, it will become easier to create new conditionals to support Varnish >= 6.1 ;-)
As a reminder, we ship actual release archives and consumers of varnish-modules are discouraged to build from git. And to keep the release engineering under control we want one archive per release, and not a matrix of branches/releases for each Varnish major version.
I'm assigning this to myself but will happily review any attempt at a pull request in this direction. If you wish to contribute to this ticket, it can be partial and doesn't have to be comprehensive at once.
dridi
commented
5 years ago
If anyone is interested in speeding up support for Varnish 6.1 and 6.2 (and why not the master branch too) we first need to remove all the bits and pieces in the source tree that enables support for 4.x and 5.x releases.
This is not hard if you are familiar with the Varnish code base, but it's tedious.
Once we are free of all those conditional code paths, it will become easier to create new conditionals to support Varnish >= 6.1 ;-)
As a reminder, we ship actual release archives and consumers of varnish-modules are discouraged to build from git. And to keep the release engineering under control we want one archive per release, and not a matrix of branches/releases for each Varnish major version.
I'm assigning this to myself but will happily review any attempt at a pull request in this direction. If you wish to contribute to this ticket, it can be partial and doesn't have to be comprehensive at once.