mail issueshttps://source.puri.sm/thomas.markiewicz/mail/issues2019-07-10T16:46:25Zhttps://source.puri.sm/thomas.markiewicz/mail/issues/3Add email account when the app runs for the very first time2019-07-10T16:46:25ZThomas Markiewiczthomas.markiewicz@puri.smAdd email account when the app runs for the very first timeAs an everyday Librem One user, I want to configure my Librem One email account when the app runs for the very first time and I want the app to remember that account so that I can subsequently launch the app straight into my inbox.
### SCOPE
* When user first downloads and starts the app, they get prompted for their account info
* When the account is setup successfully app transitions to INBOX which is an empty screen for now
* App remembers the account details and on subsequent launch notices it has an active account and so goes straight to INBOX
* Strings should be set up for internalization, but the only expected translation is English for this story
* Fetching folders, envelopes, and the mail body is out of scope
* Unit tests should cover all logic in BLoCs
* Material UI only
* Target Librem One accounts only at this point
* generic IMAP configuration is out of scope
* Librem One address must be "@librem.one"
### DONE
* [ ] Optimized for mobile and tablet screens
* [ ] Internationalized strings (only English translation for now)
* [ ] Screen mockups for mobile and tablet (light theme only for now)
* [ ] Code complete
* [ ] Unit tests complete
* [ ] Reviewed
* [ ] Merged and successfully build by CI
* [ ] QA tested on both Android and iOS
As an everyday Librem One user, I want to configure my Librem One email account when the app runs for the very first time and I want the app to remember that account so that I can subsequently launch the app straight into my inbox.
### SCOPE
* When user first downloads and starts the app, they get prompted for their account info
* When the account is setup successfully app transitions to INBOX which is an empty screen for now
* App remembers the account details and on subsequent launch notices it has an active account and so goes straight to INBOX
* Strings should be set up for internalization, but the only expected translation is English for this story
* Fetching folders, envelopes, and the mail body is out of scope
* Unit tests should cover all logic in BLoCs
* Material UI only
* Target Librem One accounts only at this point
* generic IMAP configuration is out of scope
* Librem One address must be "@librem.one"
### DONE
* [ ] Optimized for mobile and tablet screens
* [ ] Internationalized strings (only English translation for now)
* [ ] Screen mockups for mobile and tablet (light theme only for now)
* [ ] Code complete
* [ ] Unit tests complete
* [ ] Reviewed
* [ ] Merged and successfully build by CI
* [ ] QA tested on both Android and iOS
https://source.puri.sm/thomas.markiewicz/mail/issues/2Run unit tests and build iOS and Android binaries on commit to branch2019-07-09T17:44:23ZThomas Markiewiczthomas.markiewicz@puri.smRun unit tests and build iOS and Android binaries on commit to branchAs a project maintainer, I want gitlab to automatically run unit tests and build iOS and Android binaries on any commit to `develop` and `master` branches so that I can notice and fix problems as soon as they occur.
### SCOPE
* Triggered when anyone commits to `develop` branch
* Use Fastlane
* Run all unit tests and fail the build if any test fails
* Build iOS binary and fail the pipeline if iOS fails to build
* Build Android binary and fail the pipeline if Android fails to build
* Save Android binary as a build artifact
* Use a runner on the Macstadium build server
### DONE
* [ ] Build is triggered on any commit to `develop` branch
* [ ] Unit tests get executed and pipeline fails when even one test fails
* [ ] iOS binary gets build successfully
* [ ] When iOS binary fails, pipeline fails
* [ ] Android binary gets build successfully and is saved as a pipeline build artifact
* [ ] When Android binary build fails, pipeline fails
As a project maintainer, I want gitlab to automatically run unit tests and build iOS and Android binaries on any commit to `develop` and `master` branches so that I can notice and fix problems as soon as they occur.
### SCOPE
* Triggered when anyone commits to `develop` branch
* Use Fastlane
* Run all unit tests and fail the build if any test fails
* Build iOS binary and fail the pipeline if iOS fails to build
* Build Android binary and fail the pipeline if Android fails to build
* Save Android binary as a build artifact
* Use a runner on the Macstadium build server
### DONE
* [ ] Build is triggered on any commit to `develop` branch
* [ ] Unit tests get executed and pipeline fails when even one test fails
* [ ] iOS binary gets build successfully
* [ ] When iOS binary fails, pipeline fails
* [ ] Android binary gets build successfully and is saved as a pipeline build artifact
* [ ] When Android binary build fails, pipeline fails