New Release/Docker Image?

[wuast94]

i see a lot of work done in this repo but the latest release was in feb 2024?

docker images with 2.6.x build 2 month ago, 2.6.6 about 7 month ago, and so on.

it all seems very inconsistent to me. maybee im missing something but it would be very nice to see new releases on changes follwing the semver versioning.

[marziaelia]

Please check out the Release Cadence section in the main README.

You also have the option to build SFTPGo yourself if you'd like access to features that haven’t been officially released yet.

[drakkan]

I’d like to clarify that the project is not "dead for the public."

The open-source version of SFTPGo is still actively maintained. In fact, many new features have been added to the development branch and will tag a new release when time allows, just like with many other open-source projects maintained by a small team or individual contributor.

For a long time, I maintained a pinned issue requesting help from the community to keep the project fully open source. The outcome? Over a billion Docker pulls, at least two companies building their entire business around SFTPGo, many others leveraging it, and just around 30 sponsors.
Everything about the project has happened openly, transparently, and in the public eye. For years, I’ve offered the community the opportunity to shape the direction of the project.

So yes, some new features are now exclusive to the enterprise edition. That decision was not taken lightly. The alternative would have been to abandon the project altogether and focus on other work to support my family.

The open-source project is still here, still maintained, and still useful to a large number of users and compamies.

The following bug was identified in the Enterprise edition, and the fix was subsequently contributed to the open-source version:

6bde42f

Similarly, the following improvement was first added in the Enterprise edition and then included in the open-source version:

a5dd529

As you can see, the Enterprise edition also brings benefits to the open-source project.

At the end of the day, actions and long-term commitment speak for themselves.

I understand that not everyone will agree with this model, and that’s perfectly fine.
But I believe the project has always been, and continues to be, valuable and accessible to the open-source community.

That said, I’d prefer if feedback of this nature wasn’t shared from an anonymous GitHub account. Constructive discussion carries more weight when there’s transparency on both sides.

[wuast94]

first of all and like i said, i fully understand the decision to put stuff behind a paywall (espacially if its mainly enterprise features). The understanding of most people "Opensource = Free" is straight bullshit. People work for it, put time in it, and in germany we say you cant life from air and love. if someone agrees or not the route a project takes to get fundings is a another story and always will make someone mad.

the point i was focused on was the release cycle/cadence of the docker builds. because what happens there is that the enterprise version get updates frequently and the open one not all. the latest release over a year ago.

i for example use the semver tag which (when folloing the semver rules) means i had 19month no update at all.
The image was updated 7 mointh ago (didnt looked why the 2.6.x was updated 3 month ago, if semver it should point to 2.6.6 which is latest which was touched 7 month ago).
also your mentioned features/bug a month ago are technicly open but dont included in thoose.
also that should be things that should change the semver version and trigger a new release.

so again, i understand the decision you take on funding, i understand to put stuff behind a enterprise paywall. but i dont understand why this means no more semver and new builds on the public stuff.
im no coder so i cant contribute much on that side, but sometimes i can and do my contribution on some projects, and seeing them not merged at all or knowing even if they get merged i cant use them (an latest or edge tag isnt usable for me) is just not a good feeling

and to clarify, im not a buisnness at all, im burning my own private money with self hosting, on top i try to do contributions one way or the other to projects.

[helmut72]

the latest release over a year ago

https://github.com/drakkan/sftpgo/releases

Wasn't v2.6.6 released was on 24th february 2025?

[drakkan]

I appreciate the respectful tone and your understanding of the funding side of open source.

Regarding the lack of new tagged releases: the main reason is simply lack of time.
Now that I’m running a company, I have to focus on both the technical and non-technical aspects of the business. Unfortunately, this leaves me with very little spare time to manage tasks like tagging and publishing regular open builds, along with the related packaging work (Homebrew, WinGet, PPA, OSUOSL repo and other post-release steps).

At this stage, paying customers must take priority, they make it possible for the project to survive.
Without their support, SFTPGo would no longer be maintained.

That said, I do plan to tag a new release (v2.7.0) before November. The reason for this timing is that my current Azure Trusted Signing certificate (used for Windows code signing) will expire then, and unfortunately I can’t renew it anymore. Azure Trusted Signing it’s now limited to companies based in the US or Canada. I want to make sure that Windows users of the open-source version have at least one final signed release.

[wuast94]

the latest release over a year ago

https://github.com/drakkan/sftpgo/releases

Wasn't v2.6.6 released was on 24th february 2025?

thats my bad 😅 i read feb 2024 😅

@drakkan if there is something i can help on the docker side of things feel free to reach out, if i can help i will see what i can do