Adding more projects to the Project Tester

[Seb]

On Saturday, 7 July 2018 at 08:04:47 UTC, Timoses wrote:
> On Friday, 6 July 2018 at 23:56:01 UTC, Basile B. wrote:
>> On Friday, 6 July 2018 at 21:47:34 UTC, JN wrote:
>>>
>>> By the way, is there any policy for outdated dub packages?
>>
>> You just found an idea for the score algorithm.
>
> Why isn't there something like "compiler compatibility" in a 
> dub config file? E.g. currently the vibe.d project lists the 
> compiler versions the code is compatible with [1].
> Wouldn't a field in dub like
>
> "compilerCompatibility":
> {
>     "dmd": "2.080.0",
>     "ldc": "..."
> }
>
> be nice? This could also help code.dlang.org to show 
> compatibility of libraries/packages.
>
> The only pain I guess would be to keep such a list up to date.
>
> [1]: https://github.com/vibe-d/vibe.d#support

I'm not sure it's a good idea to manually hard-code such a list 
into the dub.json.
However, for every release or so, the dub registry could crawl 
all its packages and run `dub test` on them. Of course, there's 
the chance that a build still fails (e.g. due to missing 
dependencies) even though it would pass locally, but each package 
that passes with the latest registry could receive additional 
points.