2018-12-13 19:02:45 +01:00
|
|
|
|
---
|
|
|
|
|
|
id: #313-core-improvements
|
|
|
|
|
|
title: Core Improvements Swarm
|
|
|
|
|
|
status: research
|
|
|
|
|
|
lead contributor: igor
|
|
|
|
|
|
contributors:
|
|
|
|
|
|
- adam
|
|
|
|
|
|
- dmitry s
|
|
|
|
|
|
- roman
|
|
|
|
|
|
- pedro
|
|
|
|
|
|
budget:
|
|
|
|
|
|
- actual: xxx
|
|
|
|
|
|
- estimate: yyy
|
|
|
|
|
|
- currency: ETH/USD/SNT
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
# Core Improvements Swarm
|
|
|
|
|
|
|
|
|
|
|
|
## Summary and Goal(s)
|
|
|
|
|
|
|
|
|
|
|
|
Status Core Improvements swarm's goal is the preparation of Status Mobile Client to be released publicly (AppStore/GP release tracks).
|
|
|
|
|
|
|
|
|
|
|
|
A few key areas that we need to focus on:
|
|
|
|
|
|
|
|
|
|
|
|
* all the critical security and privacy issues are resolved (including audit);
|
|
|
|
|
|
- a security and privacy document is delivered (it lists guarantees we make around security and privacy; as well as ways we are falling short)
|
|
|
|
|
|
|
|
|
|
|
|
* all the critical tech debt issues are resolved;
|
|
|
|
|
|
* key UX problems are solved in two areas:
|
|
|
|
|
|
- adoption issues;
|
|
|
|
|
|
- retention issues.
|
|
|
|
|
|
|
|
|
|
|
|
The work includes releasing internal "dogfood" builds as well as betas in preparation to the public release.
|
|
|
|
|
|
|
|
|
|
|
|
### Additional contributors
|
|
|
|
|
|
- Andrea MP
|
|
|
|
|
|
- Andrei M (Design)
|
|
|
|
|
|
- Serhy/Anna/Nastya(QA)
|
|
|
|
|
|
- Rachel/Hester (PO)
|
|
|
|
|
|
|
|
|
|
|
|
## Communication
|
|
|
|
|
|
(required)
|
|
|
|
|
|
`status channel (same as Core Team)`: [`#status-core`](https://get.status.im/chat/public/status-core)
|
|
|
|
|
|
`sync frequency`: Weekly Sync Mondays, 10:00 CET (the regular "Core Team" standup)
|
|
|
|
|
|
`meeting notes`: [this running doc on notes.status.im](https://notes.status.im/sm7x7tPpQESkRwu7YNFzSQ)
|
|
|
|
|
|
|
|
|
|
|
|
# Research
|
|
|
|
|
|
|
2019-02-04 13:44:59 +01:00
|
|
|
|
### Backlog refresh
|
|
|
|
|
|
5th February — refresh and re-prioritize backlog to keep it up to date
|
2018-12-13 19:02:45 +01:00
|
|
|
|
|
|
|
|
|
|
## Specification
|
|
|
|
|
|
|
|
|
|
|
|
## Implementation
|
|
|
|
|
|
|
2019-02-04 13:44:59 +01:00
|
|
|
|
See https://www.pivotaltracker.com/n/projects/2232205
|
2019-01-21 13:25:47 +01:00
|
|
|
|
|
2019-02-04 13:44:59 +01:00
|
|
|
|
O.9.32 releases (hotfixes)
|
|
|
|
|
|
0.9.33 release in preparation (feature update)
|
2019-01-21 13:25:47 +01:00
|
|
|
|
|
2018-12-13 19:02:45 +01:00
|
|
|
|
## Maintenance
|
|
|
|
|
|
|
|
|
|
|
|
### 1. Battery usage
|
|
|
|
|
|
|
|
|
|
|
|
### 2. Application performance profiling
|
|
|
|
|
|
|
|
|
|
|
|
### 3. Mobile Releases
|
|
|
|
|
|
|
|
|
|
|
|
- [Mobile release guide](https://notes.status.im/mobile-release-guide)
|
|
|
|
|
|
- [Mobile release notes](https://notes.status.im/mobile-release-notes)
|
|
|
|
|
|
- Upgrade policy
|
|
|
|
|
|
* *User’s data.* User should be able to successfully upgrade preserving all his/her data from 0.9.19 to any beta release.
|
|
|
|
|
|
* *Messaging/Transactions.* User should be able to successfully interact (make transactions, chat, etc) with users that have 0.9.20 or later release.
|
|
|
|
|
|
|
|
|
|
|
|
## Backlog
|
|
|
|
|
|
|
2019-01-15 10:46:56 +01:00
|
|
|
|
See Pivotal Tracker: https://www.pivotaltracker.com/n/projects/2232205
|
2018-12-13 19:02:45 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Copyright
|
|
|
|
|
|
|
|
|
|
|
|
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
|
|
|
|
|
|
|
|
|
|
|
|
|
