Post #1230583
2026-03-01 09:19 UTC
@barefootstache I would expect a more useful description depending on the type and status.
* alpha/experimental, maybe with a sort of broad overview of what you can expect to work.
* beta, with a description / jssue tracker of known serious issues.
All other software I would assume should be reasonably “reliable” for the described feature set / use cases. Obviously this isn’t always true, but calling your software production/enterprise ready is just empty words to me.
Replies (1)
-
@ianthetechie@fosstodon.org 2026-03-01 09:24
@barefootstache if you want to indicate that software is mature, you can just say that (ideally with some sort of policy on release engineering, API stability, etc.). If you want to indicate that the software IS in fact being used in “production” systems then you should instead state what kind of system, scale, use case, or similar. Software in “production” could mean anything from a web app handling 2 hits per minute to a load bearing API serving thousands or req/sec.