Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consolidate release strategy #531

Open
1 of 2 tasks
fremartini opened this issue Nov 2, 2023 · 0 comments
Open
1 of 2 tasks

Consolidate release strategy #531

fremartini opened this issue Nov 2, 2023 · 0 comments
Assignees

Comments

@fremartini
Copy link
Member

fremartini commented Nov 2, 2023

Based on the new appbundle release strategy, we can no longer release development-versions as Firebase requires a published app to accept appbundles. One solution is to continue building APK's for development builds and only use AAB's for production builds which introduces an inconsistency between the builds.

I propose the following new release strategy:

Environment/Action Database Description Firebase environment
Build locally Development Connect to development environment while creating new features N/A
Open pull request to main Development Release APK with version: {branch_name (build_number)} e.g frem/consolidate_release_strategy (123) for testing Dev
Push to main Production Build Appbundle and release Preview build to Firebase Prod
GitHub release from main Production Build Appbundle and release production version Prod

Relates to #462

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant