Just wrote my cry of the soul on @forgejo Docker image tags and update practices.

https://codeberg.org/forgejo/forgejo/issues/984#issuecomment-1576575

I understand that they want to achieve a very stable working software, but I'm note really sure if they're making it right considering that they're a part of Forge Federation movement which endorses more people to have their forges as a part of the large network.

The fact that they're making users be able to subscribe only to patch-level updates is a bit crazy.

That'll make users to either invest a lot of time into upgrade process each time new minor version comes or to have an insecure installation.

You'd say: "they want their software to be stable and predictable". And I'd agree with you if they were using SemVer strategy in their development accumulating breaking changes for next major release which would happen each ~year and allow you to safely upgrade between minor versions. That would be predictable.

But currently it's almost each month or more often when unpredictable version is published and requires to proceed with updates manually.

That really pains me because I want to move from Gitea to the project which is more free and more interested in developing federation further. But Forgejo makes a lot of efforts for me to reconsider and stay on Gitea.

#Gitea #Forgejo #fork #dev #soft #git #selfhosting #migration #security