Remove PHPUnit from PHP images
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, php
- Domain
- build-system, ci-cd, devops
Research direction
Review the PHP image definitions and current PHPUnit setup, then read the linked PHPUnit release and deprecation documentation. Compare preliminary builds and tests for PHPUnit 9.6, 10.x, and 11.x; done means the feasible version or removal path is documented with its required work and PHP compatibility.
Written by the indexing model from the issue text.
Description
v9.4 (currently what we use)
- EoL occurred on February 2, 2024
- Designed for PHP 7.3
https://phpunit.de/supported-versions.html
Docs:
- https://phpunit.de/announcements/phpunit-9.html
- https://phpunit.de/announcements/phpunit-10.html
- https://phpunit.de/announcements/phpunit-11.html
- https://github.com/sebastianbergmann/phpunit/blob/9.6/DEPRECATIONS.md
- https://github.com/sebastianbergmann/phpunit/blob/10.5/DEPRECATIONS.md
- https://github.com/sebastianbergmann/phpunit/blob/11.3/DEPRECATIONS.md
Things to start watching out for now:
- deprecation warnings generated by our current version
TODO:
- Any key benefits other than bug fixes/PHP 8.x specific support?
- Build images with 9.6 to do some preliminary tests against
- Build images with 10 to do some preliminary tests against
- Decide when/if 9.6 is feasible
- How much will work will it take?
- Is it even worth it?
- Decide when/if 10.x is feasible
- How much will work will it take?
- Is it even worth it?
- Decide when/if 11.x is feasible (can we skip 10.x or will that take too much work for now?) [>= PHP 8.2]
- How much will work will it take?
- Is it even worth it?
- Dominant language
- Perl
- Stars
- 45
- Forks
- 37
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nextcloud/docker-ci
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
transifex
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
transifex
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
transifex
-
transifex
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in nextcloud/docker-ci
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
documentation Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
trizen/youtube-viewer#456 ·
-
connectivity Open
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Common US ingredient names are not recognized, so about 12.4k US products miss an allergen warning Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
openfoodfacts/openfoodfacts-server#14657 · 5 comments ·