List view
- No due date•5/5 issues closed
- No due date•113/113 issues closed
- No due date•155/155 issues closed
- No due date•135/135 issues closed
- Due by July 31, 2024•251/251 issues closed
- Due by May 30, 2024•173/173 issues closed
## OOBE (out of the box experience) - Restart OOBE development - Work with design to scope and prioritise the OOBE development to be done during this cycle ## Messaging & Communities *Priorities In priority order:* **1. Finish anything that wasn't completed in the previous 1.27 cycle** **2. Fix bugs, both functional and UX fit-and-finish defects.** - Aim to finish fixing all issues tagged with "E:Design Feedback 1.25" and "E:Design Feedback 1.25". This is because the 'Mobile UI fit and finish" co-working event will happen right after the 1.28 release, and to get maximum value from this event it would be great if all currently identified UI defects were closed before hand. - Use https://status.app/insights/epics/E:Design%20Feedback%201.25 and https://status.app/insights/epics/E:Design%20Feedback%201.24 to get view all of these UI defect issues, and how we are tracking on closing them. - Focus on bugs related Status Desktop interop with ad-hoc group chat functionality and Communities functionality, and specifically any bugs related to Status Community individual channel token gating. - Any other bugs and quality defects. **DON'T BUILD NEW COMMUNITIES OR MESSANGING FUNCTIONALITY, FOCUS IN ON FIXING BUGS AND COMPLETING LOOSE ENDS RELATED TO FUNCTIONALITY THAT'S ALREADY BEEN BUILT BUT IS NOT QUITE COMPLETE** ## Wallet **1. Continue building out Mobile Wallet MVP main screens** - By 'main screens', referring to all flows and screens in the Wallet section, excluding Wallet settings screens
Due by March 21, 2024•107/107 issues closed### This release will be used for internal dogfooding Mobile dev team priorities In priority order: **1. Finish anything that wasn't completed in the previous 1.26 cycle** **2. Select which accounts to share with each Community's control node** - Designs should be ready for review and dev feedback by 18th September **3. Settings home screen** - the settings home screen only **4. Fix bugs, both functional and UX fit-and-finish defects.** - specifically focus on bugs related to the Communities functionality, when a community is utilizing all the community admin functionality available in Status Desktop - any remaining UX quality defects - ensure all community token gating related functionality is working
Due by January 31, 2024•157/157 issues closedMobile dev team priorities In priority order: **1. Finish anything that wasn't completed in the previous 1.25 cycle** **2. Fix bugs, both functional and UX fit-and-finish defects.** - Great progress during 1.25 on fixing UX fit-and-finish defects :-) Let's aim to close all issue tagged "E:Design Feedback 1.24" by the end of this cycle. - Test all Communities functionality using the Public Test Community that will feature all types of token gating that Iuri is going to set up. - Test how Status Mobile responds to community admin changes are made in Status Desktop e.g. when a channel is added or deleted or renamed, is the correctly reflected in Status Mobile? Are changes to Community meta info like name and banner image correctly reflected in Status Mobile? Etc, etc... - We need to get our quality bar to where we want it to be, and then keep tech. debt at a roughly fixed level as we build out any additional functionality. - Going forward, as much as is sensible, all new functionality should meet the higher quality bar we are aiming for before landing. **3. Fix any remaining issues related to syncing with Desktop** **--- Things that should NOT be worked on this cycle ---** - We shouldn't start anything in Settings or Profile related ------------------------ **Mobile Wallet dev team priority:** - Continue building out Mobile wallet MVP
Due by November 9, 2023•82/82 issues closedThis release should feature: - General polish: further polish of messaging/communities/onboarding/profile" Finish resolving all the issues identified during the Porto Sprint Fix the UI polish issues that Pedro and Francesca are going to report against 1.24 Ensure that joining a community where the "Request to join required" setting is OFF works Fix syncing with Desktop bugs - Get the old wallet operational and initial work related to the new wallet - Security and privacy Allow user to change their password
Due by August 30, 2023•101/101 issues closed- Sharing: Allow users to share status content on different platforms - Polishing and completing: messaging/communities/onboarding/shell
Due by July 13, 2023•102/102 issues closed"This release should feature: - Onboarding: Allow a user to restore their account using a seedphrase - Syncing Allow a user to syncing/pair two unpaired devices - Communities User facing token gating functionality - General polish: further polish of messaging/communities/onboarding"
Due by May 22, 2023•68/68 issues closed- No due date•84/84 issues closed
- No due date•114/114 issues closed
- No due date•23/23 issues closed
- No due date•57/57 issues closed
- No due date•36/36 issues closed
- No due date•24/24 issues closed
- No due date•35/35 issues closed
- No due date•28/28 issues closed
- No due date•25/25 issues closed
- No due date•27/27 issues closed
- No due date•19/19 issues closed
- No due date•24/24 issues closed
- Due by November 23, 2020
https://notes.status.im/release-1.11-scope?edit
Due by November 3, 2020•21/21 issues closedhttps://notes.status.im/release-1.10-scope
No due date•29/29 issues closed- Due by October 26, 2020
https://notes.status.im/release-1.9-scope?edit
No due date•20/20 issues closedhttps://notes.status.im/release-1.8-scope?edit
No due date•10/10 issues closed- Due by October 12, 2020
- Due by September 28, 2020
- Due by October 6, 2020
- Due by August 26, 2020•3/3 issues closed
- Due by August 10, 2020
- Due by August 3, 2020
Bug fixes and small improvements release
Due by September 8, 2020•26/26 issues closed- Due by September 22, 2020•11/11 issues closed
- Due by August 24, 2020•13/13 issues closed
- Due by July 14, 2020•18/18 issues closed
- Due by June 8, 2020
- Due by June 1, 2020
- Due by May 25, 2020
- Due by May 10, 2020•6/6 issues closed
- Due by May 3, 2020•9/9 issues closed
- Due by April 29, 2020•1/1 issues closed
This is our wall of shame with the top 10 issues. The things we know we shouldn't be doing, but for whatever reason we are. The list came from a small group of us who met up in Basel, musing about what security should look like at Status, and what principles we all stand behind. https://our.status.im/our-wall-of-shame/
No due date•13/13 issues closedIssues and blockers required for the Q2 beta release
Due by June 20, 2018•119/119 issues closed- No due date•38/38 issues closed
- Due by January 12, 2018•5/5 issues closed