# Please stop spamming releases for single changes **URL:** \ **Category:** CoD4x | Client Support\ **Created:** [September 23, 2026, 3:55pm UTC](https://cod4x.ovh/t/please-stop-spamming-releases-for-single-changes/5555 "2026-09-23T15:55:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![kingwolf](https://cod4x.ovh/letter_avatar_proxy/v4/letter/k/bc8723/32.png) [@kingwolf](https://cod4x.ovh/u/kingwolf)\ **Post date:** [September 23, 2026, 3:55pm UTC](https://cod4x.ovh/t/please-stop-spamming-releases-for-single-changes/5555/1 "2026-09-23T15:55:13Z")
Over the past days, single minor bug fixes have been packaged and almost at this point with 21.7 feels like spam. Its good that you have revived development, but please follow standard practise group development changes as one does normally Thousands of people even today download and get patch, things break. Just compare it to 21.3 , which we stayed for multiple years, this is turning that upside down. ---
**Author:** ![proxict](https://cod4x.ovh/user_avatar/cod4x.ovh/proxict/32/2508_2.png) [@proxict](https://cod4x.ovh/u/proxict)\ **Post date:** [September 23, 2026, 4:43pm UTC](https://cod4x.ovh/t/please-stop-spamming-releases-for-single-changes/5555/2 "2026-09-23T16:43:35Z")
The standard practice is that these bugfixes would bump the patch version - that’s why it exists in semver. Unfortunately, CoD4x doesn’t yet use full semver and thus the minor version is getting bumped. The “spam” will stop once the rough edges from the latest release get ironed out, which is hopefully soon. That being said, I don’t see anything wrong with new releases coming out more regularly. It’s not that uncommon to have a rolling release development model. ---
**Author:** ![kingwolf](https://cod4x.ovh/letter_avatar_proxy/v4/letter/k/bc8723/32.png) [@kingwolf](https://cod4x.ovh/u/kingwolf)\ **Post date:** [September 23, 2026, 4:45pm UTC](https://cod4x.ovh/t/please-stop-spamming-releases-for-single-changes/5555/3 "2026-09-23T16:45:20Z")
Its not uncommon, but it is not correct approach for releasing updates for ALL players. Please test it internally, or stop the release build and publish , if thats automatic, until you get to a sizable point worth committing as a release. ---
**Author:** ![K-Faktor](https://cod4x.ovh/user_avatar/cod4x.ovh/k-faktor/32/70_2.png) [@K-Faktor](https://cod4x.ovh/u/K-Faktor)\ **Post date:** [September 23, 2026, 5:08pm UTC](https://cod4x.ovh/t/please-stop-spamming-releases-for-single-changes/5555/4 "2026-09-23T17:08:37Z")
Just uninstall the game, and it will be easier to install the releases. ---
**Author:** ![proxict](https://cod4x.ovh/user_avatar/cod4x.ovh/proxict/32/2508_2.png) [@proxict](https://cod4x.ovh/u/proxict)\ **Post date:** [September 23, 2026, 5:46pm UTC](https://cod4x.ovh/t/please-stop-spamming-releases-for-single-changes/5555/5 "2026-09-23T17:46:49Z")
Not the correct approach according to what rules? It is a standard rolling release. Whether that’s the best approach is debatable, but it’s not “correct” nor “incorrect”. But it is perfectly valid. What does “test it internally” mean? I’ve sent the new release version to a few players for testing and they’ve played with it for about a week. There is no internal team. Getting to a sizable point in terms of new features doesn’t mean anything when these past few releases after 21.4 have only been bugfixes. If you have a better way of ensuring that players aren’t stuck with a buggy game, I will happily take your advice. PS: I am planning to convert the versioning semantic to semver, but that will require server changes. When that’s done, it will be possible to do patch releases. And I want to add a config into the updater where players will be able to choose between “nightly” and “stable” builds. PPS: I would love to adapt the server to the same updating mechanism as is used in the client now, i.e., pulling the latest release directly from GitHub. I have kind of been putting it on the back burner, but anyone is welcome to take a stab at it themselves, which I would appreciate. ---
**Author:** ![kingwolf](https://cod4x.ovh/letter_avatar_proxy/v4/letter/k/bc8723/32.png) [@kingwolf](https://cod4x.ovh/u/kingwolf)\ **Post date:** [September 25, 2026, 7:24pm UTC](https://cod4x.ovh/t/please-stop-spamming-releases-for-single-changes/5555/6 "2026-09-25T19:24:48Z")
I mean generally that just group fixes together and then release them, no need to have a release for each new commit or fix. That seems excessive. You are going down the argumentative rabbit hole there a bit ---
**Author:** ![proxict](https://cod4x.ovh/user_avatar/cod4x.ovh/proxict/32/2508_2.png) [@proxict](https://cod4x.ovh/u/proxict)\ **Post date:** [September 26, 2026, 1:23pm UTC](https://cod4x.ovh/t/please-stop-spamming-releases-for-single-changes/5555/7 "2026-09-26T13:23:57Z")
Then I would have to wait a month to wait for more bugs to get reported. I see no harm in releasing the bugfixes right away - players who run into the bugs they report probably like seeing them getting fixed sooner rather than later. My point is, I don’t see what the problem is with releasing more frequently even if they are just small bugfixes.