Ping @DenisChenu

<compatibility>
    <version>4.0</version>
    <version>5.0</version>
    <php>7.2</php>
</compatibility>

Comments?

Edit, urgh at less-than sign...

Remind :
compatibility VS tested …

I mean : for example : currently : i set reloadAnyReponse to compatibility 5, and i set to beta1, beta2 etc … but only for 5.X …

Then : you need to allow enable plugin at user risk …
Some of my plugins : i just have to update the version: 4 to 5, i let user make the test (if not a client)

If i have to add php compat … i need to test it … I don't make 8.X test currently … i just test on my server. I want user report issues with other PHP version …

And : need to add

• IIS test (windows directory)
• PATH/GET url test

And : most important

• postgrey
• mariadb
• MSSQL
  etc …

Hmmm. Good points. A good CI pipeline can at least test for PHP compatibility. Testing for db is harder, requires manual or unit tests.

A good CI pipeline can at least test for PHP compatibility.

Yes, but i see only complete solution with LimeSurvey core hack and update here.

Adding (and activate) all plugins…
And you know : fix an issue is really quick BUT fix an issue AND add a test is really more complex and time consuming …