v1.4.0 is out, this build targets v1.5.0.
Subscribe to this discussion for development updates
v1.4.0 is out, this build targets v1.5.0.
Subscribe to this discussion for development updates
Out of curiosity, in this build will it be possible to recover from the archive the issue of changing the LESS compiler in order to upgrade to Font Awesome 6?
Darkle hello brother , ilove what you did with https://brickrr.com/ is there away we can talk ?
Abdel mueenulit As this is not really related to the development diary, I'll answer you in this other discussion (https://discuss.flarum.org/d/31261-discussion-liste-layout)
Hello!
We had a kickoff meeting for the 22th Build (v1.5) where we went over pull requests and issues for v1.5. We also went over our public Roadmap to revisit our priorities.
In the past 2 weeks, we have merged over 20 pull requests including bug fixes , performance improvements
, and even some features
.
We will try posting more frequent development updates.
will you support chinese search in the version 1.5?
now i use google search to instead
Looking forward to supporting Chinese search.
Hey everyone!
We've released a new version (v1.4.1) of flarum/statistics
to fix some performance issues loading the admin dashboard on very large communities.
You can update with:
composer update flarum/statistics:"*"
php flarum migrate
php flarum cache:clear
We are halfway through the development cycle of build 22, working towards v1.5.0 and already close to 100 commits have been contributed to Flarum.
That's 40 commits more than what we delivered for v1.4.0 !
It is August 21st. We are one month and ten days from the v1.4 release and already 113 commits have been made, that's 53 more than our last release
Here's an overview, from my point of view, of what has been happening.
In addition to all this, we've been making some plans to make the recently build Proposals section carry more weight. As we've allowed not only proposals for core, but also for new or existing extensions, we considered ways to reduce the staleness; the risk that zero action is taken on valid proposals.
For this reason, we are preparing the introduction of Blomstra Payments with its Bounty feature. Once we have finished the terms required for this feature on Discuss, we will enable Bounties under the Proposals tag. There are quite a few considerations to do this properly, but we're hoping this will help incentivize more proposals to be completed sooner and attract more developers to our ecosystem. Obviously whoever funds a proposal will gain the much valued Devotee badge!
Now that we're implementing the Payments extension we're also going to centralize our donations by leveraging the Pay to Access feature it offers. In essence this is a way to gain access to a Group/Badge through a subscription. Our Open Collective and GitHub Sponsors page obviously will remain up as well, but we'll no longer be granting badges to people donating through those channels, in fact we will be removing badges from existing users soon. So, if you cherish your old "Backer" badge (now renamed Supporter), make sure to subscribe here on discuss once we have the feature enabled!
All great stuff! Love it!
For those of you receiving email notifications from discuss (who doesn't ), we are now sending from
community@apps.flarum.org
. So please check your spam folder and/or add the mail address to the allow list.
Background: due to the unreliable nature of our mailserver we are moving back to managed services; including sendgrid for outbound email and possibly migadu for mailboxes.