FileBrowser Quantum comes with 2 main release flavors. Choosing the right version is an important first step to getting started.

Release Types

Stable Release

The stable release build is the most reliable version as the name implies. It gets updated less frequently, but is ideal for:

  • Those getting started with FileBrowser Quantum
  • Users with a userbase that doesn’t want to see occasional bugs
  • Production environments requiring stability
  • Anyone who prefers proven, tested features

Beta Release

The beta release build is ideal for those who:

  • Don’t have a large userbase
  • Want the latest features immediately
  • Are comfortable with potential issues
  • Want to contribute to development

Release Cadence

One major difference is the release cadence between the two versions:

Stable

~ 1 to 3 months

Beta

~ 1 to 3 weeks

Feature Differences

Eventually, stable release gets all the same features as beta releases, but they lag behind the release schedule. Because of this, features may not come to stable for a month or two.

Other than that, the releases are identical in functionality between major versions.

Version Number Meaning

Versioning follows semantic versioning in format and I try to follow the process version increment. This means:

Major version update (v1.0.0 → v2.0.0)

An overhaul of major features or compatibility differences.

Minor version update (v1.0.0 → v1.1.0)

Can include a collection of features and changes that shouldn't cause any major compatibility issues. All changes should be made in a backwards compatible way.

Patch version update (v1.0.0 → v1.0.1)

For bugfixes, and other minor changes that don't impact functionality.

When to Move to Beta Instead of Stable?

I definitely need and welcome anyone that wants to use beta – it’s the best version! But it’s also most likely to see issues.

So, I would recommend using stable unless there’s a feature you need that only exists in beta.

If you move to beta, please join the discussions on GitHub and raise issues for things you see. Having an active beta community is one thing that helps make stable … stable.

What If Stable Has Bugs?

There are two types of bugs in stable:

  1. Known Bugs:
    • Bugs that have existed and are known. Perhaps they require big changes to make work or there’s some other non-trivial reason it’s in stable. Please search GitHub for the issue and see if it is known or if there’s a fix coming that may exist in beta. These type of issues need to be fixed over a longer period of time in beta to ensure there’s no additional unintentional changes as a result of the bugfix.
  2. New Bugs:
    • Bugs that are new and trivial. These bugs probably also exist in beta and have not been discovered yet. If this does happen and the fix is clear and simple, I may update stable directly with a patch release.