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

Capybara

Absolutely, yes — I have no concerns about 2.0.0-rc-8, my dozens of users are all happy with it. Finally I'll be able to build my extensions only for the stable new version — I'm actually just finishing up an extension for adding friends

Wlork

Karl Anything FoF or other Dev Work should not be categorized with the Flarum Core itself 🙂

I know, but anyone using the old version of this extension can have issues with the migration, which is why I posted a quick reminder 🙂

Karl could you please share the bugs for Flarum Core that needs addressed? If it's not shared, there is no remedy.

I know, thanks. The minor visual bug will be reported tomorrow in GitHub 🙂 I'm going to sleep 😁

ram0ng1

flarum I'm satisfied with the performance of RC.8

Forogramero

I have only found two minor bugs, but coming from extensions not the core itself, so, from me is a rotund yes.

dragsugur

my forum is very active (just today single thread got 3.2k posts) and using v2 since i think rc 4 or 3.
rc8 is the best visible perfomance upgrade (r5 was taking too much cpu power when too many people viewing and intearcting with a single posts, now its waay better.), and i dont see any problems. (if you need any real logs just let me know!)

my only thing would be messages extension is not very good currently but thats not the core core.

happy to see finally releasing v2 and looking forward for the future.

ram0ng1

dragsugur I remember you mentioning you were making a theme back when I started with the Avocado theme... Up until now, I had never seen your forum live in production (only screenshots). Now I can say I really liked your forum's theme!

ernestdefoe

ram0ng1 yeah I was thinking the same thing. It does look pretty sharp.

dragsugur

ram0ng1 thank you its so good to hear this from you. im planning to change profile pages and give it an overhaul a new design.

Capybara

dragsugur What a beautiful forum!

Walys

Sorry , I voted no by mistake.
I just wanted to scroll down and accidentally clicked no. I've looked for how to delete or change the vote, but it won't let me.

Note for version 2.0:
Leave the vote editing for a couple of minutes. 😅

Karl

Walys we get it man, you're hard to please /s 😛

Subarist

dragsugur
Haha, I finally got to see the mysterious forum! 😄 It’s even more impressive seeing it live.

Subarist

RC3 was already in pretty good shape with no major issues for me.
Since RC6, I don't think I've had any reason to complain to IanM about it feeling slow. 😄

My view is still pretty much the same as before: more than 99% of users sitting in front of their devices using a forum won't actually notice what has fundamentally changed in V2.
And that's despite the fact that, from a developer's perspective, V2 is a completely refreshed architecture.

From my point of view, the most important thing is simply that the response speed should not be worse than V1. If it meets that bar, it's already a perfectly valid release.
And now, it's actually fast.

There will always be code that needs fixing and things that can be improved. That's just software development.
But I think the time has come. 100% yes from me. 👍

CyberGene

My forum has been running 2.0 since the first release candidate and has been very stable (and I’ve actively reported various small issues that got fixed with each new release candidate). With the latest performance optimizations it became ultra fast and responsive. My forum is not a heavily customized forum and we don’t rely on some exotic extensions. To me it’s absolutely perfect now, I don’t have any complaints, even minor ones, so to me RC8 should become the official 2.0 release.

werter

There is no need to rush, for a diamond to become a brilliant it needs to be polished...

Found what looks like a related regression in the same area: external links
(links to a different domain, e.g. youtube.com) inserted via the post editor's
"insert link" button now open in the same tab/window instead of a new one.

Historically, Flarum core has added target="_blank" rel="noopener noreferrer"
to all external links in post content (see flarum/framework859 from the 1.x
era, where this was implemented in Formatter.php). This appears to no longer
be happening as of rc.8.

Steps to Reproduce:

Create a new post
Use the editor's "insert link" toolbar button to add a link to an external
site (e.g. https://youtube.com) with some link text
Submit the post
Click the rendered link

Expected: Link opens in a new tab (as it historically has).
Actual: Link opens in the same tab, navigating away from the forum.

This may share a root cause with the internal-link redirect bug reported in
#5012 — both point to the link-attribute logic in Formatter.php possibly
having regressed during the 2.0 rewrite.

Environment: Flarum core 2.0.0-rc.8, same install as #5012.

Forogramero

dragsugur only thing would be messages extension

I recommend you : CHAT from @ram0ng1 . You can have Private Chat (private message/chatroom) and also public channels. Beautiful built-in. No need for BByou (which didn't work well for me) or private message extensions. They feel outdated if you compare it with CHAT - DISCOURSE LIKE THEME.

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