2025.03 Release Tracking #10369

Open
opened 2025-03-01 14:32:14 +00:00 by pastk · 11 comments
Member

Expected Store Submission: 2025-03-02
Expected Full Rollout: 2025-03-07
Release Manager: @rtsisyk

Please post status updates as comments on this ticket while progressing through the checklist. Include links and/or screenshots where applicable.

  • The data generator is running
  • The release notes are drafted in Etherpad
  • No blockers in 2025.03 milestone.
  • A PR with the release notes is raised.
  • A PR with the new data is raised
  • QA sign-off:
    • Master has been tested manually on Android by @rtsisyk.
    • Master has been tested manually on Android by @vng.
    • Master has been tested manually on iOS by @rtsisyk.
    • Master has been tested manually on iOS by @vng.
    • Master has been tested by Android Monkey on the latest master.
  • A PR with the new data has been merged into master.
  • A new release release/2025.03.02 branch has been created from master.
  • Metaserver is updated to include new data version
  • Data synchronization has been started
  • Android Beta pipeline went through on release/20XX.MM.DD branch.
  • iOS Beta pipeline went through on release/20XX.MM.DD branch.
  • AppStore metadata, screenshots, and keywords are merged into git.
  • "App Store Version Release" in the AppStore draft set to "Manually release this version".
  • A PR with the release notes has been merged into master.
  • Android Release pipeline went through on release/20XX.MM.DD branch.
  • The iOS App draft in AppStore has the same date as the release (20XX.MM.DD).
  • An iOS build from the iOS Beta pipeline has been submitted to review to "Public" testers in TestFlight.
  • "Build" in the AppStore draft set to the build created by the iOS Beta pipeline.
  • iOS Release pipeline went through on release/20XX.MM.DD branch - only metadata, without screenshots.
  • "Phased Release for App Store Automatic Updates" in the AppStore draft set to "Release update over 7-day period using phased release".
  • AppStore (PROD) has been sent to review.
  • Android signed APK from Google Play has been uploaded to the GitHub Release as OrganicMaps-YYMMDDNN-google-release.apk.
  • Android Web (OrganicMaps-YYMMDDNN-web-release.apk) and Google Play (OrganicMaps-YYMMDDNN-google-release.apk) APKs are shared in Telegram with the release notes.
  • Google Play Production sent for a review with automatic 10%1% phased rollout
  • Data is synchronized
  • iOS RC TestFlight is approved
  • iOS RC TestFlight link is published on Telegram with the release notes.
  • F-Droid knows about the new build.
  • Google Play Closed Beta is approved and published via Managed Publishing to 100%.
  • Google Play Managed Publishing Check
  • Android RC is sent for review to Huawei AppGallery with manual release (TBD)
  • Metaserver is updated to include new app versions
  • Google Play 20% phased rollout
  • The release final sign-off
    • Firebase reports by TBD
    • Google Play reports by TBD
    • TestFlight reports by TBD
    • Email & Telegram reports by TBD
  • AppStore 100% rollout
  • Google Play 100% rollout
  • App Gallery 100% rollout
  • GitHub - remove "pre-release" and mark the release as "latest"
  • F-Droid build status check
  • The release branch is merged into master
  • News Publishing
    - [ ] Publish Telegram news post
    - [ ] Publish the announcement on Fosstodon
    - [ ] Publish the announcement on X (Twitter)
    - [ ] Publish news on the website
    - [ ] Publish the announcement on Facebook
    - [ ] Publish the announcement on Instagram
    - [ ] Publish the announcement on Reddit
    - [ ] Publish the announcement on LinkedIn
**Expected Store Submission:** 2025-03-02 **Expected Full Rollout:** 2025-03-07 **Release Manager:** `@rtsisyk` Please post status updates as comments on this ticket while progressing through the checklist. Include links and/or screenshots where applicable. - [x] The data generator is running - [x] The release notes are drafted in Etherpad - [x] No blockers in [2025.03 milestone](https://github.com/organicmaps/organicmaps/milestone/14). - [x] A PR with the release notes is raised. - [x] A PR with the new data is raised - [ ] QA sign-off: - [ ] Master has been tested manually on Android by `@rtsisyk.` - [ ] Master has been tested manually on Android by `@vng.` - [ ] Master has been tested manually on iOS by `@rtsisyk.` - [ ] Master has been tested manually on iOS by `@vng.` - [ ] Master has been tested by [Android Monkey](../.github/workflows/android-monkey.yaml) on the latest master. - [x] A PR with the new data has been merged into master. - [x] A new release `release/2025.03.02` branch has been created from master. - [x] Metaserver is updated to include new data version - [x] Data synchronization has been started - [ ] [Android Beta](../.github/workflows/android-beta.yaml) pipeline went through on `release/20XX.MM.DD` branch. - [x] [iOS Beta](../.github/workflows/ios-beta.yaml) pipeline went through on `release/20XX.MM.DD` branch. - [ ] AppStore metadata, screenshots, and keywords are merged into git. - [ ] "App Store Version Release" in the AppStore draft set to "Manually release this version". - [x] A PR with the release notes has been merged into master. - [ ] [Android Release](../.github/workflows/android-release.yaml) pipeline went through on `release/20XX.MM.DD` branch. - [ ] [The iOS App draft in AppStore](https://appstoreconnect.apple.com/apps/1567437057/distribution/ios/version/deliverable) has the same date as the release (`20XX.MM.DD`). - [x] An iOS build from the iOS Beta pipeline has been submitted to review to "Public" testers in [TestFlight](https://appstoreconnect.apple.com/teams/92fab819-8b15-4d04-bd75-2bd32b523c3f/apps/1567437057/testflight). - [ ] "Build" in the AppStore draft set to the build created by the iOS Beta pipeline. - [ ] [iOS Release](../.github/workflows/ios-release.yaml) pipeline went through on `release/20XX.MM.DD` branch - **only metadata, without screenshots**. - [ ] "Phased Release for App Store Automatic Updates" in the AppStore draft set to "Release update over 7-day period using phased release". - [x] AppStore (PROD) has been sent to review. - [ ] Android signed APK from Google Play has been uploaded to the GitHub Release as `OrganicMaps-YYMMDDNN-google-release.apk`. - [ ] Android Web (`OrganicMaps-YYMMDDNN-web-release.apk`) and Google Play (`OrganicMaps-YYMMDDNN-google-release.apk`) APKs are shared in Telegram with the release notes. - [ ] Google Play Production sent for a review with automatic <s>10%</s>1% phased rollout - [x] Data is synchronized - [ ] iOS RC TestFlight is approved - [ ] iOS RC TestFlight link is published on Telegram with the release notes. - [x] F-Droid [knows about the new build](https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/app.organicmaps.yml). - [ ] Google Play Closed Beta is approved and published via Managed Publishing to 100%. - [ ] Google Play Managed Publishing Check - [ ] Android RC is sent for review to Huawei AppGallery with manual release (TBD) - [ ] Metaserver is updated to include new app versions - [ ] Google Play 20% phased rollout - [ ] The release final sign-off - [ ] Firebase reports by TBD - [ ] Google Play reports by TBD - [ ] TestFlight reports by TBD - [ ] Email & Telegram reports by TBD - [ ] AppStore 100% rollout - [ ] Google Play 100% rollout - [ ] App Gallery 100% rollout - [ ] GitHub - remove "pre-release" and mark the release as "latest" - [x] F-Droid build status check - [ ] The release branch is merged into master - [ ] News Publishing - [ ] Publish Telegram news post - [ ] Publish the announcement on Fosstodon - [ ] Publish the announcement on X (Twitter) - [ ] Publish news on the website - [ ] Publish the announcement on Facebook - [ ] Publish the announcement on Instagram - [ ] Publish the announcement on Reddit - [ ] Publish the announcement on LinkedIn
Author
Member
  • Metaserver is updated to include new data version
  • Data synchronization has been started

Data sync should be finished first and only then the metaserver could be updated, isn't it?
Otherwise there is a risk the metaserver will direct clients to servers with absent or incomplete map sets.

> * [ ] Metaserver is updated to include new data version > * [ ] Data synchronization has been started Data sync should be finished first and only then the metaserver could be updated, isn't it? Otherwise there is a risk the metaserver will direct clients to servers with absent or incomplete map sets.
Author
Member
- https://git.omaps.dev/organicmaps/organicmaps/pulls/10371
Author
Member
- https://git.omaps.dev/organicmaps/organicmaps/pulls/10377
Author
Member
- https://github.com/organicmaps/meta/pull/96
Owner
https://github.com/organicmaps/organicmaps/tree/release/2025.03.02 https://github.com/organicmaps/organicmaps/actions/runs/13617163076/job/38061716177 https://github.com/organicmaps/organicmaps/actions/runs/13617166780
Author
Member
Re-run after relnotes merge: android https://github.com/organicmaps/organicmaps/actions/runs/13617570634/job/38062640405 ios https://github.com/organicmaps/organicmaps/actions/runs/13617630854
Author
Member

android https://github.com/organicmaps/organicmaps/actions/runs/13617570634/job/38062640405

GP upload failed; seems like because of addition of another FG service

       "errors": [
         {
           "domain": "global",
           "message": "You must let us know whether your app uses any Foreground Service permissions.",
           "reason": "forbidden"
         }
> android https://github.com/organicmaps/organicmaps/actions/runs/13617570634/job/38062640405 GP upload failed; seems like because of addition of another FG service - https://git.omaps.dev/organicmaps/organicmaps/pulls/10284 ``` "errors": [ { "domain": "global", "message": "You must let us know whether your app uses any Foreground Service permissions.", "reason": "forbidden" } ```
Owner

android https://github.com/organicmaps/organicmaps/actions/runs/13617570634/job/38062640405

GP upload failed; seems like because of addition of another FG service

* [Add foreground service to indicate about ongoing downloads #10284](https://git.omaps.dev/organicmaps/organicmaps/pulls/10284)
       "errors": [
         {
           "domain": "global",
           "message": "You must let us know whether your app uses any Foreground Service permissions.",
           "reason": "forbidden"
         }

The new declaration is on review with old bundle. I will push a new bundle as soon as they approve the old one.

> > android https://github.com/organicmaps/organicmaps/actions/runs/13617570634/job/38062640405 > > GP upload failed; seems like because of addition of another FG service > > * [Add foreground service to indicate about ongoing downloads #10284](https://git.omaps.dev/organicmaps/organicmaps/pulls/10284) > > > ``` > "errors": [ > { > "domain": "global", > "message": "You must let us know whether your app uses any Foreground Service permissions.", > "reason": "forbidden" > } > ``` The new declaration is on review with old bundle. I will push a new bundle as soon as they approve the old one.
Owner

AppStore - day 1 of phased rollout:

Image
AppStore - day 1 of phased rollout: <img width="696" alt="Image" src="https://github.com/user-attachments/assets/3e5d226e-36a9-4bfb-995e-5b3eaff166f9" />
Author
Member

The release is published on F-Droid already.

The release is published on F-Droid already.
vng commented 2025-03-06 15:36:45 +00:00 (Migrated from github.com)

IMO, 20% for 2 days and 100% after is enough in our situation, instead of 7 days rollout.

IMO, 20% for 2 days and 100% after is enough in our situation, instead of 7 days rollout.
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: organicmaps/organicmaps#10369
No description provided.