From 856d3d4a80740a74f61d83d5c9e6bb30bd436bd5 Mon Sep 17 00:00:00 2001 From: Rami Abou Ghanem Date: Thu, 13 Feb 2020 14:27:45 -0500 Subject: [PATCH 1/5] Add release process to README --- gallery/README.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/gallery/README.md b/gallery/README.md index 0118479514a..343014dbb15 100644 --- a/gallery/README.md +++ b/gallery/README.md @@ -72,3 +72,28 @@ more details): ``` flutter pub run grinder update-code-segments ``` + +## Creating a new release (for Flutter org members) + +1. Bump the version number up in the `pubspec.yaml`. Use semantic versioning to determine + which number to increment. For example `2.2.0+020200` should become `2.3.0+020300`. + +1. Create a tag on the `master` branch in the form of `gallery-v2.3`. + +1. Publish the web release (using the peanut package). + 1. `flutter pub global activate peanut` + 1. `flutter pub global run peanut:peanut` + 1. `git push upstream gh-pages:gh-pages` (You may have to force push) + +1. Publish the android release (using the correct signing certificates) + 1. Create the app bundle with `flutter build appbundle` + 1. Upload to the play store console + 1. Publish the play store release + 1. Create the APK with `flutter build apk` (this is for the Github release) + +1. Draft a release in Github from the tag you created, call the release `Flutter Gallery 2.3` + 1. Upload the Android APK from above + 1. Create and upload the macOS build by running `flutter build macos` and zipping the + app inside `build/macos/Build/Products/Release`. + 1. Optional: Create and upload the linux/windows builds + 1. Publish the release From b22160444c235c286181daa709e0e47d38341d83 Mon Sep 17 00:00:00 2001 From: Rami Abou Ghanem Date: Thu, 13 Feb 2020 14:30:25 -0500 Subject: [PATCH 2/5] Update nested list --- gallery/README.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/gallery/README.md b/gallery/README.md index 343014dbb15..879482a3d53 100644 --- a/gallery/README.md +++ b/gallery/README.md @@ -81,19 +81,19 @@ flutter pub run grinder update-code-segments 1. Create a tag on the `master` branch in the form of `gallery-v2.3`. 1. Publish the web release (using the peanut package). - 1. `flutter pub global activate peanut` - 1. `flutter pub global run peanut:peanut` - 1. `git push upstream gh-pages:gh-pages` (You may have to force push) + * `flutter pub global activate peanut` + * `flutter pub global run peanut:peanut` + * `git push upstream gh-pages:gh-pages` (You may have to force push) 1. Publish the android release (using the correct signing certificates) - 1. Create the app bundle with `flutter build appbundle` - 1. Upload to the play store console - 1. Publish the play store release - 1. Create the APK with `flutter build apk` (this is for the Github release) + * Create the app bundle with `flutter build appbundle` + * Upload to the play store console + * Publish the play store release + * Create the APK with `flutter build apk` (this is for the Github release) 1. Draft a release in Github from the tag you created, call the release `Flutter Gallery 2.3` - 1. Upload the Android APK from above - 1. Create and upload the macOS build by running `flutter build macos` and zipping the - app inside `build/macos/Build/Products/Release`. - 1. Optional: Create and upload the linux/windows builds - 1. Publish the release + * Upload the Android APK from above + * Create and upload the macOS build by running `flutter build macos` and zipping the + app inside `build/macos/Build/Products/Release`. + * Optional: Create and upload the linux/windows builds + * Publish the release From 649fe02bcf65454dbc38c6280281e47ec325f7f7 Mon Sep 17 00:00:00 2001 From: Rami Abou Ghanem Date: Thu, 13 Feb 2020 14:31:18 -0500 Subject: [PATCH 3/5] Update nested list again --- gallery/README.md | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/gallery/README.md b/gallery/README.md index 879482a3d53..ea621ebea11 100644 --- a/gallery/README.md +++ b/gallery/README.md @@ -78,22 +78,22 @@ flutter pub run grinder update-code-segments 1. Bump the version number up in the `pubspec.yaml`. Use semantic versioning to determine which number to increment. For example `2.2.0+020200` should become `2.3.0+020300`. -1. Create a tag on the `master` branch in the form of `gallery-v2.3`. +2. Create a tag on the `master` branch in the form of `gallery-v2.3`. -1. Publish the web release (using the peanut package). - * `flutter pub global activate peanut` - * `flutter pub global run peanut:peanut` - * `git push upstream gh-pages:gh-pages` (You may have to force push) +3. Publish the web release (using the peanut package). + * `flutter pub global activate peanut` + * `flutter pub global run peanut:peanut` + * `git push upstream gh-pages:gh-pages` (You may have to force push) -1. Publish the android release (using the correct signing certificates) - * Create the app bundle with `flutter build appbundle` - * Upload to the play store console - * Publish the play store release - * Create the APK with `flutter build apk` (this is for the Github release) - -1. Draft a release in Github from the tag you created, call the release `Flutter Gallery 2.3` - * Upload the Android APK from above - * Create and upload the macOS build by running `flutter build macos` and zipping the - app inside `build/macos/Build/Products/Release`. - * Optional: Create and upload the linux/windows builds - * Publish the release +4. Publish the android release (using the correct signing certificates) + * Create the app bundle with `flutter build appbundle` + * Upload to the play store console + * Publish the play store release + * Create the APK with `flutter build apk` (this is for the Github release) + +5. Draft a release in Github from the tag you created, call the release `Flutter Gallery 2.3` + * Upload the Android APK from above + * Create and upload the macOS build by running `flutter build macos` and zipping the + app inside `build/macos/Build/Products/Release`. + * Optional: Create and upload the linux/windows builds + * Publish the release From b3e9a0be6516455ff3b97352862a68d517e8d307 Mon Sep 17 00:00:00 2001 From: Rami Abou Ghanem Date: Fri, 14 Feb 2020 10:21:21 -0500 Subject: [PATCH 4/5] Address feedback --- gallery/README.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/gallery/README.md b/gallery/README.md index ea621ebea11..550df17be7c 100644 --- a/gallery/README.md +++ b/gallery/README.md @@ -78,7 +78,9 @@ flutter pub run grinder update-code-segments 1. Bump the version number up in the `pubspec.yaml`. Use semantic versioning to determine which number to increment. For example `2.2.0+020200` should become `2.3.0+020300`. -2. Create a tag on the `master` branch in the form of `gallery-v2.3`. +2. Create a tag on the `master` branch of this repo in the form of `gallery-v2.3`. + * `git tag gallery-v2.3` + * `git push --tags` 3. Publish the web release (using the peanut package). * `flutter pub global activate peanut` @@ -86,14 +88,14 @@ flutter pub run grinder update-code-segments * `git push upstream gh-pages:gh-pages` (You may have to force push) 4. Publish the android release (using the correct signing certificates) - * Create the app bundle with `flutter build appbundle` - * Upload to the play store console - * Publish the play store release - * Create the APK with `flutter build apk` (this is for the Github release) + * Create the app bundle with `flutter build appbundle`. + * Upload to the play store console. + * Publish the play store release. + * Create the APK with `flutter build apk` (this is for the Github release). 5. Draft a release in Github from the tag you created, call the release `Flutter Gallery 2.3` - * Upload the Android APK from above + * Upload the Android APK from above. * Create and upload the macOS build by running `flutter build macos` and zipping the app inside `build/macos/Build/Products/Release`. - * Optional: Create and upload the linux/windows builds - * Publish the release + * Optional: Create and upload the Linux/Windows builds. + * Publish the release. From 943f5b6c8d98f81cdd7be93c28e1923e7c61ced5 Mon Sep 17 00:00:00 2001 From: Rami Abou Ghanem Date: Tue, 18 Feb 2020 11:39:12 -0500 Subject: [PATCH 5/5] Address feedback --- gallery/README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/gallery/README.md b/gallery/README.md index ea621ebea11..562f9b13ea5 100644 --- a/gallery/README.md +++ b/gallery/README.md @@ -80,15 +80,16 @@ flutter pub run grinder update-code-segments 2. Create a tag on the `master` branch in the form of `gallery-v2.3`. -3. Publish the web release (using the peanut package). +3. Publish the web release (using the [peanut package](https://pub.dev/packages/peanut)). * `flutter pub global activate peanut` * `flutter pub global run peanut:peanut` - * `git push upstream gh-pages:gh-pages` (You may have to force push) + * `git push upstream gh-pages:gh-pages` + * `git update-ref refs/heads/gh-pages upstream/gh-pages` if you need to align with upstream. -4. Publish the android release (using the correct signing certificates) +4. Publish the Android release (using the correct signing certificates) * Create the app bundle with `flutter build appbundle` - * Upload to the play store console - * Publish the play store release + * Upload to the Play store console + * Publish the Play store release * Create the APK with `flutter build apk` (this is for the Github release) 5. Draft a release in Github from the tag you created, call the release `Flutter Gallery 2.3`