-
-
Notifications
You must be signed in to change notification settings - Fork 287
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
docs: first-jab at the release process #4567
Conversation
|
||
## 1. Pre-release Checklist | ||
|
||
Before you proceed with the release, ensure the following: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we say "we" instead?
@@ -0,0 +1,63 @@ | |||
# Open Food Facts - Flutter App - Release Guide | |||
|
|||
Welcome to the release guide for the Open Food Facts Flutter App. Below are the steps to guide you through our 2 weeks release process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A diagram may be interesting to sum up the process (I can create one if necessary)
RELEASE.md
Outdated
|
||
- [ ] All the features and fixes planned for this release are merged into the `main` branch. | ||
- [ ] All merged features and fixes have corresponding unit and integration tests. | ||
- [ ] Update version number in the `pubspec.yaml` according to [semantic versioning](https://semver.org/). (Mergin Release Please should take care of that, and also provoke a F-Droid release up to a week later.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is one is false, as it's done by the GitHub Action when we release.
I've already tried to say it was a bad idea, but the answer was a NO
RELEASE.md
Outdated
2. Trigger the automated CI process which will handle the build and deployment for both iOS and Android. | ||
3. [Go to the Play Console](https://play.google.com/console/u/0/developers/4712693179220384697/app/4972942602078310258/tracks/internal-testing), and add a changelog | ||
4. [Go to App Store Connect](https://appstoreconnect.apple.com/apps/588797948/testflight/ios), and select audiences to distribute to in the Testflight section, and add a Testflight changelog | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An explanation for F-Droid would also be interesting here
Codecov Report
@@ Coverage Diff @@
## develop #4567 +/- ##
===========================================
- Coverage 10.34% 10.32% -0.03%
===========================================
Files 296 296
Lines 15340 15410 +70
===========================================
+ Hits 1587 1591 +4
- Misses 13753 13819 +66 see 4 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
What
doc: first-jab at the release process