Lines Matching refs:We

10 We could push our code directly to production, which would be fast yet less safe since we never tes…
17    - (a) We can create builds for production use only.
18 …- (b) We can create builds for production use and separate builds for pre-production change testin…
20    - (a) We can test changes with TestFlight and Play Store Internal Track.
21    - (b) We can test changes with an internal distribution build.
22 …- (c) We can test changes with Expo Go or a [development build](/develop/development-builds/introd…
24    - (a) We can publish updates to a single branch.
25    - (b) We can create update branches that are environment-based, like "production" and "staging".
26 …- (c) We can create update branches that are version-based, like "version-1.0", which enables us t…
28 We can mix, match, and tweak the parts above to create a process that is the right balance of relea…
65 - There are no pre-production checks to make sure the code will function as intended. We can test w…
69 This flow is like an un-versioned variant of the "branch promotion flow". We do not track release v…