this post was submitted on 05 Jan 2025
36 points (100.0% liked)

Selfhosted

40960 readers
477 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hi, I am the developer of PdfDing. One thing I am not sure about is the frequency of my releases. What do you folks prefer in self-hosted projects? More releases in order to get new features as fast as possible or fewer releases with bigger feature additions?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 28 points 5 days ago (1 children)

This isn't something that should really be set by users of an app. It should be set by you, as you will be the one to handle user feedback and bug reports.

That being said, bigger releases are a challenge from a debugging report standpoint because you are introducing many more changes in each release compared to a smaller number of charges in more frequent releases. This is why many devops teams in corporate land try to keep releases smaller and more frequent (see also: Agile Development)

[–] [email protected] 3 points 5 days ago

Very good point about Agile.

As an end-user (that is, the IT staff that will be deploying/managing things), I prefer less-frequent releases. I'd love to see 1 or 2 releases a year for all software (pipe dream, I know). Once you have a handful of packages, you end up with constant change to manage.

I suspect what we end up with is early adopters embracing the frequent releases, and providing feedback/error reporting, while people like me benefit from them while choosing to upgrade less frequently.

There are about 3 apps that I'm a beta tester for, so even I'm part of that early-adopter group.