Minor releases should get a new build/tag even they are no longer officially supported
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, php, wordpress
- Domain
- build-system, devops, release
Research direction
The issue names no specific files, tests, or entry points. Review the repository's image build and tag configuration, then compare how maintained WordPress minor releases and their PHP versions are represented. Done means supported security minor releases receive Docker builds and tags using the appropriate older PHP major version.
Written by the indexing model from the issue text.
Description
These minor releases are mainly to fix security vulnerabilities. Although WordPress does not officially support these major versions (for new features), they are still being maintained if there are issues to security. (Similar to how Google releases security patches to Android after those devices will no longer receive a new Android version upgrade.)
Right now, NONE of these SECURITY minor releases are being released for the Docker community. Not every site can be directly upgraded to the latest WP major version due to plugin & theme compatibility issues on WP or PHP versions. (Consider production sites that cannot migrate to a new version until they are fully tested and approved.)
Note that those maintained versions should release w/ latest on the same EOL PHP major version (since WP did not drop support for PHP 5.6+ as of today). (e.g. PHP 5.6 -> PHP 7 is a major breaking upgrade, so PHP 5.6 should still be built with (for those minor releases on the maintained WP versions.)
Ref: https://github.com/docker-library/wordpress/issues/399#issuecomment-489814805
- Dominant language
- Shell
- Stars
- 2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 docker-library/wordpress
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
docker-library/wordpress#959 · 1 comment · 2 reactions ·
-
New php-latest tag Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
docker-library/wordpress#930 · 6 comments · 4 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
docker-library/wordpress#927 · 3 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
docker-library/wordpress#862 · 7 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
docker-library/wordpress#835 · 2 comments · 2 reactions ·
All issues in docker-library/wordpress
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
community-scripts/ProxmoxVE#17425 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ll7/robot_sf_ll7#9560 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·