Shouldn't this target 2.8 ?

i figured master because of

That should be submitted on master: we shouldn't change the version on a patch release. (#29439 (comment))

so this changes the default version; for 2.8 users can leverageSYMFONY_PHPUNIT_VERSION=8.2

We should maybe remember to bump before the 4.4.0 if a new version is released meanwhile.

We should definitively not forget to bump to v8 :)

Im wondering about the purpose of hardcoding the upper bound constraint for PHPUnit :/ it blocks therequire phpunit/phpunit case and let Composer decide the stable version 🤔 Not doing so,
would make tools likehttps://github.com/jakzal/toolbox (installing simple-phpunit on a Docker image) always make simple-phpunit install the latest stable phpunit by default.

AFAIK it's not possible to do e.g.SYMFONY_PHPUNIT_VERSION=@stable due some hardcoded version checks, which maybe arent needed as php 7 (?) (#31948)

it's not possible to do e.g. SYMFONY_PHPUNIT_VERSION=@stable due some hardcoded version checks

did you try relaxing those? now that we use composer to download phpunit, maybe it could be made to work?

@nicolas-grekas IIUC ideally the default for sf4.4 as of php7.2 would be@stable right? To avoid having to invokeSYMFONY_PHPUNIT_VERSION=@stable simple-phpunit all the time.

And im not sure doing it as of php7.2, if we dont need the version upfront i tend to prefer not hardcoding any upper limits 🤔

I'm not sure: what about BC when a new major of phpunit is released?

Ultimately let the user decide its fixed version usingSYMFONY_PHPUNIT_VERSION=x.y?

Having@stable by default seems sensible :/

Isn't it already the case? See
https://github.com/symfony/recipes/blob/master/symfony/phpunit-bridge/4.1/phpunit.xml.dist

I see, let's leave as is. Explicit version control is nice anyway. Basically i was looking for a cheap solution to lethttps://hub.docker.com/r/jakzal/phpqa/ install both a wrapped v7 and v8 by default. But it's distributed from 7.1 to 7.3, so v8 should be excluded for 7.1

The toolbox also installs v7 + v8 natively under different binaries:https://github.com/jakzal/toolbox/blob/master/resources/tools.json#L618-L641

This works because it can exclude 7.1 tag-based per tool, but not per install command for a single tool. As simple-phpunit is a version manager it doesnt make sense to have e.g.simple-phpunit + simple-phpunit-7.

Therefor im leaning to exclude the whole simple-phpunit binary in the toolbox, on 7.1. (cc@jakzal), then it can be installed usingSYMFONY_PHPUNIT_VERSION=8.2 simple-phpinit install without relying on any defaults in SF.

I figured PHPunit 7 can also be bumped.

Thank you@ro0NL.