---
# System prepended metadata

title: v1.5 Kickoff meeting

---

# v1.5 Kickoff meeting

## v1.4 retrospect
- short release, little activity.
- QA went well, get more people on QA from community.

## Who is available for the next cycle
- Sami
- Sasha towards the end perhaps
- Daniël
- David
- Ian

## v1.5
- Ian will focus more on bundled extensions going forward.

### Pull Requests
- throttling endpoints, for review.
- #3548 david w fix tests on static caching pr
- add a helper to tests to easily debug (print request data on failure)
- use constant for route names in the controllers and reference.
- #3529, delete all notifications, sami fixes tests
- #3456, stacked modals requires review
- #3421, we would rather move with type on the discussion not the first post.


### Glowingblue
**How to tackle the request by GlowingBlue to generalize Flarums' opinionatedness towards discussions, like using app.discussions everywhere; see https://docs.pat.dev/fKjq2_dUQoKodr077hZ4FQ?view**

- Not enough use cases/examples from glowingblue about how they're implementing their extensions.
- Start by making discussions slowly flexible.
- Blog extension, Knowledge base.
- Devs hacking around re-using discussions, could be cleaner.
- -> Look at blog, build simpler blog with custom discussion type, **find out the complexities ourselves**?
- Answer them on their hackmd, pass it on to the team first.

### Issues
- https://github.com/flarum/framework/issues/3554 find out when they stopped working. (could be an extension, core poits to the right place).
- #3440, bundle it? republish assets on cache clear?
- Cache clearing issue: queue can have no locale, sends broken emails.
  - Trigger a queue restart on cache clearing. (Ian will do it!)
- (+issue) RecompileFrontendAssets needs rewriting
    - doesn't actually recompile, but should
    - not extensible, eg fof/nightmode
- #3429, i18n slug handling

## v1.x
### Roadmap progress (https://github.com/orgs/flarum/projects/22/views/1)
- Jest, let's postpone for now and look at this when we're closing in on planning 2.0
- Prevent burnout by trying too hard to push, we need to entice and engage with the community.

## State of the monorepo
- reduce google action builds/workflows, merge them
- improve experience for (new) developers to start working on framework
- tyescript local development experience.
- flarum tests are a pain locally
- dev docker image

## v2.0
### Can we prioritize the roadmap items for v2.0 so that we can tackle one of them?
- let's tackle v1.x backlog first and foremost, then start planning what we need in v1.x before 2.0 (package manager improved update notice, typescripts etc)
- then plan 2.0, not sooner