Are we actually following the semantic versioning rules?

[beliven-daniele-sarnari]

Hello maintainers 😊

We have been using your docker images as base images for a few months and we are pretty happy with it 😀!
We refer to the full tags, for example v3.3.0.

We were thinking of updating minor by minor each time without checking if the image broke some things, but by replacing some files like /etc/nginx/nginx.conf.template, /etc/nginx/site-opts.d/http.conf.template and https.conf.template, it happened to us a few times that even just one minor broke the image.

For example, this change here marked as a minor change, #437, is actually potentially a major for those who were using the feature waiting for an ENTRYPOINT behavior.

We wanted to know what you think about it @jaydrogers, thanks!

[jaydrogers]

I'm always working to improve on my software development skills, but yes -- one could argue that was a major change. At the time I tried communicating the change on Twitter and through the Github release notes, but I understand the sometimes messages can get buried amongst other communications.

I'm always trying to improve. I've learned a lot since v3.4 and I will be more aware for future releases.

I always try to do a good job on the release notes and I recommend everyone to subscribe for notifications: https://serversideup.net/open-source/docker-php/docs/getting-started/upgrade-guide#subscribe-to-repository-updates

[beliven-daniele-sarnari]

Hi @jaydrogers,
no need to apologize at all — you're doing a great job with this project! 🙌

Really appreciate the honest response. Let’s see how things go with future releases 😊

Just wanted to ask if you think it would make sense to also release Docker tags based only on the major version — for example, alongside 8.4-fpm-alpine-v3.5.0, maybe also have a tag like 8.4-fpm-alpine-v3. That could help users who want to upgrade minor by minor without risking unexpected breaking changes.

Thanks again!