Is Flarum 2.0.0-rc.8 ready to become 2.0 GA? Vote now!

flarum · 2026-08-29T21:20:00+00:00

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. 🗳️

dragsugur

Forogramero its based on realtime but im using pusher extension with soketi
and at this point its too hard for me to move every custom live feature to realtime.

Karl

dragsugur there is another option... 😛

dutchbavarian

flarum would be great to have a "Show me the results" option 😉 . We don't run 2.0 but plan to update as soon as it is final. So I am interested to see the results only.

IanM

dutchbavarian that's a fair comment. I've altered the permissions on the poll

registered users can now see the results without voting
registered users can now change their vote, if they decide to do so

dragsugur

Karl how 👀

Karl

dragsugur you just have to ask for help!

luceos

I'm only running 2.x on Elated right now, and it seems to be doing just fine. The number of available, compatible extensions is also large enough to make the newer version appealing and configurable. Very glad to see this release come to fruition after the efforts of such great people like @IanM and @SychO.

The fact that 2.x found it's roots in the NLNet/European Union's NGI zero entrust fund at 50.000 euro granted to the foundation, makes 2.0 the first release that had help from such an income stream 👏

navindra

I just had a chance to install RC8 on PianoTell up from RC5 I think, but without the MariaDB upgrade.

RC8 is working great so far and is lightning fast! Well done!

Forogramero

flarum Three hours ago I started updating my forum from 1.18 to RC8 V2.0. After a few minor issues with some extensions (especially the “circular dependencies” ones), I have to say that the 2.0 core is really fast and also feels very solid and stable (I never felt that way with v1.18). I’m amazed at how fast it is. Tomorrow and the day after I’ll keep working on the site’s custom CSS, JS and HTML (I think that will slow it down a bit, but that’s my own problem anyway).

Gentlemen of the Flarum Foundation, good job!!

If some day I become rich, I'll be your number one sponsor. 🤘🏻🤣🤗 You give valuable architecture to the internet, and u're changing the way it works.

tobcro

RC8 is fine here as well. My stage forum runs it now, and cant wait for the stable release (yes, I think its time)!

Forogramero

Update on my forum after installing RC8 v2.0:

The forum is running like a dream!

I’m a conservative person when it comes to experimental things. I won’t deny that I was nervous about going ahead with the installation, because I thought I was stepping into the unknown.

To my surprise, it turned out to be remarkably easy and straightforward when you follow the process step by step and don’t overcomplicate things.

To everyone out there who is nervous about RC8: folks, go ahead and upgrade, because it’s one of the best things you can do for your forum. Don’t be afraid.

Thank you to the Flarum team for all your hard work and outstanding technical quality!

Félicien

Hello,
I’m currently migrating the champis.net site (phpBB) to Flarum 2 (champis.dev with htaccess protection: champis / wohzeJ-cywqu2-vokwoq), and everything is working very well. The site is becoming much more modern and responsive. Congratulations to the team on a job well done. I’m looking forward to the upcoming launch.
I don’t have any bugs to report; everything seems to be working very well.

Subarist

Félicien
Great migration! I honestly couldn’t tell at first which one was phpBB and which one was Flarum. 😄
Welcome, and congratulations on the new Flarum site! 🎉

Gerriet

In the share Option for this thread, I see Facebook, Whatsapp, but what is with mastodon ? Why not this in the share as option ?

ClaudiusH

Gerriet Mastodon wasn't yet added as a sharing option to the FoF Share Social extension. Mastodon itself just added a share target page in March 2026: https://blog.joinmastodon.org/2026/03/a-new-share-button/ - Seems like now would be a good opportunity to ask for Mastodon to being added.

luceos

Gerriet mastodon is federated. Even if one instance exists, most aren't on it. Eg I am on fosstodon.

Gerriet

Thanks @ClaudiusH and @luceos for your answers ;D That is what I like in this community, all time a hug for any user ;D

Morgan

Thanks to everyone's help here, I'm on rc8 and quite happy with it. It's quick, it's smooth, it's pretty, and it fixed a bunch of smaller pain points I was having with 1.8

Thank you for all your efforts, I'm excited to see the heights 2.0 reaches in the future. To my mind it's already in a really solid and stable spot.

SpikeNit

RC8 is working super fast for me. I’m looking forward to the move to 2.0!

« Previous Page