...
Question | Answer | Next steps |
|---|---|---|
When will Shannon get a release candidate of the framework with this measure? | MobileToolbox 1.6.0 for iOS has been released as a swift source package: https://github.com/MobileToolbox/MobileToolbox/releases/tag/1.6.0 |
|
What are the icons, colors, labels, etc. needed to add this as a shared assessment? |
|
|
Why are they aggregating the result file rather than adding multiple files (one for each sub-assessment) with a schema for validating that assessment? | ||
Is NU aware that their study launch date of Mid-July is put at risk by QA of their assessment (and framework) because of work we had put off doing to limit the QA for the ICAR measures? | With the focus on a speedy ICAR release, we held features back from the standard release cadence. This MCM study would run with the same known production state that we already have in our live studies – ie without the planned improvements unless we coordinate the release cadence timeline and build. Additionally, it means that current live studies would also not have the planned improvements | Weigh the pros and cons to build the release timeline |
There are already two identifiers in the v1.5.0, build 117 app. MyCogMobileV1 MyCogMobileShortV1 Why are they changing the identifier? | ||
What changes to the frameworks (other than the task identifier) are planned between now (June 13) and study launch in mid-July? | ||
Why aren’t they using the shared app code (v1.5.0) to release a version of the app where they can control the release cycle? | ||
...