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
{{ message }}
This repository has been archived by the owner on Apr 13, 2020. It is now read-only.
This issue needs some thought about whether or not it should be done, and if so, to what extent/in what way.
Background
At the moment, JTime gets big deployments which I plan to keep doing as I have found people don't like getting lots of updates to Android apps (or more specifically, get annoyed at the constant notifications about updates). However, with the last 2 deployments, I have encountered unexpected issues when the automated deployment occurred, necessitating me to manually deploy or fix the automated deployment. Continuously deploying to a staging environment could help spot these issues earlier.
Questions to be resolved
Out of JTime-rest, JTime-website and JTime-android, which should have a staging environment thing?
How should db schema modifications be handled?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue needs some thought about whether or not it should be done, and if so, to what extent/in what way.
Background
At the moment, JTime gets big deployments which I plan to keep doing as I have found people don't like getting lots of updates to Android apps (or more specifically, get annoyed at the constant notifications about updates). However, with the last 2 deployments, I have encountered unexpected issues when the automated deployment occurred, necessitating me to manually deploy or fix the automated deployment. Continuously deploying to a staging environment could help spot these issues earlier.
Questions to be resolved
The text was updated successfully, but these errors were encountered: