docs(roadmap): tentative roadmap for Q1 of 2026 #19540
Conversation
jrainville
requested review from
a team,
alaibe,
glitchminer,
osmaczko,
sunleos and
vkjr
and removed request for
a team
Jenkins Builds
|
✔️ status-desktop/e2e/prs-windowsPR19540 🔹 ~24 min 🔹 30089b1 🔹 📦 tests/e2e-windows package |
jrainville
left a comment
jrainville
left a comment
There was a problem hiding this comment.
One thing we talked about in the Release Process meeting is defining Key Features marking the cut of the release.
I think we should mark those with a star (⭐ ) in the roadmap so that it's clear to everyone that once those features are done, we will cut the release and anything not done should be pushed to the next release. Since every new feature should be behind a feature flag, it shouldn't affect anything.
In this case, I would propose the following features as Key Features:
- Mobile feature parity
- Mobile Dapp browser
- Privacy Mode
What do you guys think?
There was a problem hiding this comment.
Thanks a lot @jrainville for this update. I’ve left a few comments and suggestions.
docs/roadmap.md
Outdated
| - [Memory and Performance improvements](https://github.com/status-im/status-desktop/issues/18296) | ||
| - No provided FURPS at the moment as this is mostly about profiling and fixing issues found. | ||
| - In Progress ⏳ 🟩🟩🟩⬜⬜ 64% | ||
| - [Improve Token List and Support custom tokens](https://github.com/status-im/status-desktop/issues/19517) |
There was a problem hiding this comment.
It might be a good idea to run some testing across the following areas, as they could reveal additional tasks for this epic:
- Permissions
- Mint
- Airdrop
- Profile Showcase / Collectibles
- Join Community, Share Addresses and Community Requirements Check flows
- Manage Token Settings
There was a problem hiding this comment.
Yes, the Epic linked is actually the known bugs and things to fix related to the feature. I don't think it's worth listing all of those here, but we should for sure test all of those as part of it before releasing!
|
jrainville
left a comment
jrainville
left a comment
There was a problem hiding this comment.
Thanks for the review @noeliaSD !
Regarding the Mobile Feature Parity section, we currently list five independent features under this epic. Would it make sense to prioritise them individually? Some of these features may be more relevant or impactful than others.
My own opinion is that they are all necessary for the Mobile app to behave at lest as good at the old app, so I'd like to have them all in 2.38.
I'll still list them all in a bullet list under it so it's easier to follow. Let's see what the team and community think, ie can some of them be de-scoped?
docs/roadmap.md
Outdated
| - [Memory and Performance improvements](https://github.com/status-im/status-desktop/issues/18296) | ||
| - No provided FURPS at the moment as this is mostly about profiling and fixing issues found. | ||
| - In Progress ⏳ 🟩🟩🟩⬜⬜ 64% | ||
| - [Improve Token List and Support custom tokens](https://github.com/status-im/status-desktop/issues/19517) |
There was a problem hiding this comment.
Yes, the Epic linked is actually the known bugs and things to fix related to the feature. I don't think it's worth listing all of those here, but we should for sure test all of those as part of it before releasing!
✔️ status-desktop/prs/linux/x86_64/tests-ui/PR-19540#2 🔹 ~14 min 🔹 95f20b4 🔹 📦 tests/ui package |
✔️ status-desktop/e2e/prs-windowsPR19540 🔹 ~26 min 🔹 95f20b4 🔹 📦 tests/e2e-windows package |
jrainville
force-pushed
the
docs/q1-roadmap
branch
from
95f20b4 to
b98f027
Compare
✔️ status-desktop/prs/android/arm64/package/PR-19540#3 🔹 ~9 min 56 sec 🔹 b98f027 🔹 📦 android/arm64 package |
✔️ status-desktop/prs/linux/x86_64/tests-ui/PR-19540#3 🔹 ~18 min 🔹 b98f027 🔹 📦 tests/ui package |
✔️ status-desktop/e2e/prspr19540 🔹 ~17 min 🔹 b98f027 🔹 📦 tests/e2e package |
✔️ status-desktop/e2e/prs-windowsPR19540 🔹 ~21 min 🔹 b98f027 🔹 📦 tests/e2e-windows package |
Jenkins BuildsClick to see older builds (11)
|
3 participants
Description
Here is the tentative Status App for Q1 of 2036
@sunleos , @alaibe and I met to discuss the features everyone in the team put in the brainstorming document and prioritized them. We only got up to the 2.38 features, but that's enough to give an idea of the start of the year.
The rest of 2.39 will be added later.
This PR is open to comments from everyone, feel free to recommend what to prioritize, if we missed anything, etc.