Release 2.2.0

[ialokim]

Here are the steps to follow when preparing a new release (some custom tasks added for this release). Please check the following boxes with an x when done:

• update PTE to the latest commit at opentransitmap and run ./update-dependency-pinning.sh
• re-enable SBB (Switzerland) with new data source Switzerland: SBB Not work. #768
• re-enable PL (Poland) with new data source https://gitlab.com/opentransitmap/public-transport-enabler/-/commit/693d84e340f1525366e6b29a32c0a81401f326ff (needs more investigation as to which area is actually covered)
• test the app (automatically using AndroidTest as well as manually), paying special attention to changes since the last release
• fix any bugs if necessary
• update translations from Transifex using tx pull --mode=developer -a in the root folder (you need proper permissions to do that)
• add newly supported languages to the two arrays in app/src/main/res/values/arrays.xml
• revise the commits to master since the last release and add interesting changes (as well as new languages) to the changelog at app/src/main/res/xml/changelog_master.xml, then run python3 ./fastlane/generate_changelog.py
• bump the versionCode and versionName in app/build.gradle
• re-enable Transportr for inclusion in F-Droid Update fdroid release #826
• file another PR updating all dependencies which should be merged after the successful release

Please also refer to #689 as an example.

[ialokim]

• fix any bugs if necessary

several issues reported: #889 #890 https://gitlab.com/opentransitmap/public-transport-enabler/-/issues/6

In order to get the release out soon, I'd consider them as being non-release-blocking.

[Altonss]

• fix any bugs if necessary

several issues reported: #889 #890 https://gitlab.com/opentransitmap/public-transport-enabler/-/issues/6

In order to get the release out soon, I'd consider them as being non-release-blocking.

Indeed, #889 and #890 don't seem to be new issues related to this release.

[M00NJ]

Could #872 be a part of this release as well?

[ialokim]

Could #872 be a part of this release as well?

I don't think this is a good idea, given that we want to publish the release soon, and #872 brings a lot of UI changes that need a thourough testing.

[Altonss]

Tested this 2.2.0 release branch, and didn't encounter any issue! Great job @ialokim 👏
I think the new version could be released soon :)

[Altonss]

For the changelog I suggest something like:

- Switch to new map library (maplibre).
- Fix bugs: remember preferred means of transport, fix blank `About > Libraries` page.
- Update PTE data library: transport networks fixes and removals.
- Remove following networks: Finland, Portugal, Hungary, Czech Republic, Ghana, California, Oregon, New York, Ontario, Quebec, British Colombia, Costa Rica, Nicaragua, Florianópolis (Brazil), Brazil, New Zealand.
- Disable temporarily broken endpoints: VOR, STV, VVV and WienerLinien (Austria), Belgium, 9292 (Netherlands).

[mesinger]

@ialokim any way i can help to get this release done?

[Altonss]

Thanks for all the work @ialokim! Everything looks fine to me!
A few general comments (aside from those in the code):

• Why updating strings for pl network navitia that is for now removed? IMHO it clutters a bit the PR with useless strings.
• Should we merge Fix potential UI glitch when transport type is not given #894 before 2.2.0 ? Edit: Let's do it after :)
• Shouldn't we also mention in the changelogs that we've re-added VRS?
• Encountered an unrelated issue (is already present in 2.1.5): background color of changelog is dark when in light mode. (Opened Background color of changelog is dark when in light mode. #909)

[grote]

Technically, we didn't make it back, yet ;)

[ialokim]

Yeah it's the next unchecked bullet point in the first post, but we cannot continue without tagging the release :P

[ialokim]

And we will make it back (I hope)! 😄

[ialokim]

Thanks for your review @Altonss!

* [ ]  Why updating strings for pl network navitia that is for now removed? IMHO it clutters a bit the PR with useless strings.

There are a lot of leftover strings from now removed regions which should probably be cleaned properly at some point. But you are right, those are unfortunately really useless. I've removed them now manually.

* [ ]  Shouldn't we also mention in the changelogs that we've re-added VRS?

Good catch, added that!

[Altonss]

Looks good to me!

[Altonss]

Ready to merge and tag the release?

[grote]

Thanks everyone who contributed to this release. You are awesome! :D

I just pressed the button and the release is out. However, Google Play doesn't accept it: Google Api Error: Invalid request - Target SDK of artifact is too low: 124. It seems it is currently 32 which won't work anymore. Please see https://support.google.com/googleplay/android-developer/answer/11926878 for details.

[Altonss]

I just pressed the button and the release is out. However, Google Play doesn't accept it: Google Api Error: Invalid request - Target SDK of artifact is too low: 124. It seems it is currently 32 which won't work anymore. Please see https://support.google.com/googleplay/android-developer/answer/11926878 for details.

That shouldn't be too hard to fix, I'll try to do it :)

[Altonss]

@grote Target SDK issue should be fixed with #910