You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Initial work
* Support parsing user permissions from the API
* Ignore Sentry events in debug builds
Fixes#59
* A lot of work on permissions enforcement
* Work on insufficient permissions composable
* Add required permissions dialog
* Finish up permissions improvements
* Fully implement permissions error alert
* Callout UI work
* Warning callout if you can't see hidden teams
* Detekt style fixes, remove TODOs
* Style
* Add Detekt to concourse PR pipeline steps
* Fix detekt-check inputs
* Fix run-detekt task input/output mapping
* Fix path
* Minor copy edit
* Add release management info to readme
* Flesh out release management instructions
* Address review comments
* hopefully maybe fix callout padding
* Increase overall padding on missing teams callout
* Style
* Add detekt to build-main job
Co-authored-by: Evan Strat <[email protected]>
| 0/1/2 | Very low or low priority | UI touchups that don't impact functionality, releases with options to opt-in to beta features | No prompt initially. Optional prompt starting 14 days after release. Immediate update 21 days after release. |
127
+
| 3 | Medium priority | Medium-priority bug fixes, performance improvements, non-time-sensitive feature launches | No prompts for the first 3 days. Optional starting 4 days after release. Immediate update 21 days after release. |
128
+
| 4 | High priority or time-sensitive | High priority bug fixes, time-sensitive feature launches | Optional for the first 24 hours, then immediate. |
resource didn't trigger a new build. We can disable old versions of the resource to trigger a new
148
+
build.
149
+
4. If the Concourse [build-release job](https://concourse.sandbox.aws.robojackets.net/teams/information-technology/pipelines/apiary-mobile/jobs/build-release)
150
+
finishes successfully, you'll find a new draft release on the Internal Test track in Google Play.
151
+
At this point, you should do some small QA efforts to verify the new build. Post in #apiary-mobile
152
+
to have some people help you test. Note that access to the internal test track must be granted via
153
+
the Google Play Console.
154
+
1. Internal testers may need to uninstall the app to see the update if it was recently published.
155
+
6. If no issues are found, it's time to release! Promote the build to the Production track in
156
+
Google Play, add release notes, and save the release.
157
+
7. Google Play typically spends a day or two reviewing the release, then makes it available. In
158
+
general, expect it to take at least ~24 hours for a production release to be available to users.
0 commit comments