Dev Diary: Build 17

We're hoping to release a stable version as the next release. Seeing how we kept up with a regular release cycle (best team ever ) you understand that this release is coming fairly soon . After years of being in beta the future of Flarum is about to change for good.

All of you who have stuck around since Toby started with the kickstarter or joined soon after will probably share my relief of reaching this milestone. Those who have been with us on this journey for years have guaranteed we kept going forward, sharing in our highs and lows.

Much has changed, the team now pushing us forward in no way resembles the one of the early betas. We relied heavily on the new teams that formed and outperform what the small team managed to do in the past. Where usually one person pushed forward on the release, we already notice a much more decentralized feeling of responsibility. Our traineeship has given us an increased number of capable core developers, allowing us to grow the core team to a sensible size for the ambitions we have. It is definitely something that we strive to keep doing going forward.

I am proud to stand at the helm of this vessel as primus inter pares, steering towards an orange dawn. Our sails are catching a strong wind, the crew cheerful for what will come.

Flarum would never have come so far without the sacrifices made by many volunteers.

luceos We're hoping to release a stable version as the next release.

Little update from me:

Working on completely overhauling our js building system and asset serving infrastructure. Right now we combine all of our js files into one big file we serve on every reload that contains the entire front end. I'm not going to go super in depth here because I'm still not 100% sure how it's going to look but a guest user doesn't need to load things like the post/discussion composer because they don't have access to it. I'm going to be splitting out components or pages into their individual components that will only be loaded when needed by the client. This should improve load time across the board. This likely won't be in the next release...

luceos We're hoping to release a stable version as the next release.

4101990000
在国际社区交流请使用英文。
Flarum目前似乎还没有图床，请自行找寻相关插件。
这种问题请单独发帖，而不是在开发日记下面回复。

Please use English when communicating in the international community.
Flarum does not seem to have an image uploader at present, please find the relevant plug-in by yourself.
Please post this kind of question separately instead of replying under the development diary.

edev Can't wait for stable version of Flarum!

Same!!! I love this...I have always used phpBB or SMF, but this takes the lead in my opinion.

19 days since the last update. Is it just me or does time fly even faster these days?

• You can now track the Milestone progress directly from Discuss (https://discuss.flarum.org/milestone). Thanks to @SychO for this awesome extension!
• We are nearing the Quality Assurance week for Build 17, supposedly v1.0; it's a matter of weeks really
• @askvortsov ran a test with the badges on the avatars (https://discuss.flarum.org/d/27057)
• The foundation became owner of Flarum.es, we're doing our best to protect our brand name (which isn't always easy or cheap).
• And a ton of other stuff I seriously have a hard time remembering

almalino v0.16 is already stable IMHO

Stable to us means that the code that extensions interact with does not change that much after stable (up to the next major release). So yeah, Flarum is stable, whether extensions break between beta's? Most likely.

Did you know that while typing a reply you can browse around your forum and the composer minimizes but is still available? Did you also know that if you want to quickly go back to the discussion that you are writing a reply to, you can click the title on the composer screen (next to your avatar)?