Is Flarum 2.0.0-rc.8 ready to become 2.0 GA? Vote now!
Following on from the release of 2.0.0-rc.8, we'd love to get your opinion on whether this release should be tagged as 2.0.0 — officially bringing Flarum 2.x into stable.
This is the vote we've been building toward all along. The plan has always been that a release candidate which holds up in the real world becomes 2.0.0 stable, unchanged — and rc.8 is that candidate. Whether it crosses the line isn't a call we make alone; it's yours as much as ours. So here it is.
What you're voting on
A simple yes or no: should 2.0.0-rc.8 be tagged as 2.0.0 stable, as-is?
- A yes means: I've run it (or followed closely enough to have a view), and I think it's ready.
- A no means: not yet — and ideally, here's why. A "no" with a reason is the most useful thing you can leave in this thread. It isn't a vote against the release; it's a vote for getting it right.
There's no wrong answer, and no pressure to land on "yes." An honest "not yet, because X" is worth far more than a reflexive "ship it" - we'd really rather hear the problem now than the morning after tagging stable.
Before you vote
The vote only means something if it's grounded in reality, so if you can:
- Run rc.8 on a real forum —
composer update -W, then php flarum migrate and php flarum cache:clear. Back up first; a staging copy is ideal.
- Use it like your members would for a bit - post, search, moderate, upload, whatever your forum actually does.
- Then vote, with your own forum as the evidence.
Can't run it yourself but you've followed the RC cycle closely? Your read still counts - just weight it accordingly.
Help us triage: must-fix-now vs. later
Just as important as reporting problems is helping us weigh them, because not everything found has to be fixed before 2.0 ships. When something comes up, the question we'll be asking is:
- Does it block 2.0? Data loss, a security issue, a broken upgrade path, a regression from the previous release, or something with no workaround - these are must-fix-now. They hold the stable tag, and they're a reason to vote no.
- Or can it wait? A rough edge, a nice-to-have, a cosmetic issue, or something an extension or a bit of CSS can work around - these can land in a 2.0.1 or 2.1 without holding 2.0 back. Vote yes and note them separately; they won't be forgotten.
Holding 2.0 indefinitely for every last polish item helps no one; shipping 2.0 with a genuine blocker helps no one either. Tell us what you hit and how much it actually hurts, and we'll draw that line together.
What happens next
- If the vote lands clearly yes and nothing blocking surfaces, the next step is tagging
2.0.0 - the release this has all been building toward.
- If it's no, we fix what's holding it and go again. That's exactly what the RC process is for; it's not a failure, it's the system working.
Either way, the decision gets made in the open, by the people it affects.
Found a bug while testing? Reports still go where they always do - core bugs to the issue tracker, security privately to security@flarum.org. This thread is for the verdict; those are for the details.
Cast your vote below. 🗳️
