Merge editorialized release notes and 18.5.0.3 into develop#17346
Merge editorialized release notes and 18.5.0.3 into develop#17346
develop#17346Conversation
I say "editorialized" because we didn't go through editorial this time, but wrote them ourselves.
We plan to do some ASO experiments, and therefore will end up with manually curated keywords in multiple locales. Verbatim translation from English is therefore no longer necessary and would actually risk undoing some of the curation work because of how our automation works.
I was expecting it to be removed automatically, but wasn't the case.
|
You can trigger an installable build for these changes by visiting CircleCI here. |
| #. translators: Keywords used in the App Store search engine to find the app. | ||
| #. Delimit with a comma between each keyword. Limit to 100 characters including spaces and commas. | ||
| msgctxt "app_store_keywords" | ||
| msgid "social,notes,jetpack,writing,geotagging,media,blog,website,blogging,journal" | ||
| msgstr "" |
There was a problem hiding this comment.
We'll no longer translate keywords so that we can experiment with ASO using localized Fastlane files (keywords.txt) as the source of truth and not risk the GlotPress automation overriding them.
…elease_1.64.1 Integrate gutenberg-mobile release 1.64.1
Generated by 🚫 dangerJS |
AliSoftware
left a comment
There was a problem hiding this comment.
✅ release_notes.txt updated for WP and JP
✅ .po file updated for WP and JP
Podfile, but not the related version bumps in xcconfig 🤔
LGTM overall, but:
- Left a question to check if it was intentional that the Jetpack keywords were still translated (while the WordPress ones are not anymore). I think it's intentional, but just wanted to flag to be sure.
- The fact that this PR contains the update in
Podfile/Podfile.lockaboutgutenberg 1.64.1but not the app version bumps inxcconfigmakes me think you haven't done the related beta yet?
Which means it would be odd to merge this PR as is with half the changes for the beta (G but not xcconfig) in it. I think it makes sense to wait for you to do the beta and have the version bump included in this PR before merging it all (hence why I'm just commenting not approving)
…nt-error-messages Fix/17344 - Close account error messages
|
The Buildkite failure on I'm hoping this was just a glitch or network issue, so I just restarted it in Buildkite, let's hope and see… |
Confirming that was intentional. Since no work has been done on Jetpack and, as far as I know, no work is planned either, I left the Jetpack keywords setup through GlotPress.
That must be a byproduct of this PR being straight from the I try to use a merge branch only when necessary (i.e. when I know there would be conflicts trying to merge into I'm going to start a new beta for that and the localization fixes soon. |
developdevelop
AliSoftware
left a comment
There was a problem hiding this comment.
New commits added:
- ✅ Version bump in
xcconfigfor new beta - ✅ Update of
.stringsfile with latest GlotPress translations
Gutenberg version didn't generate a conflict because at the time of this writing, develop is still pointing to 1.64.0 (and not a new 1.65.0-alpha* which would have been the case if a new feature or fix for Gutenberg had been necessary for a feature worked on in develop in the meantime), so should be all good to merge as is!
| ## ===================== | ||
| ## | ||
| gutenberg :tag => 'v1.64.0' | ||
| gutenberg :tag => 'v1.64.1' |
There was a problem hiding this comment.
I'm surprised that develop is not yet on an v1.65.0-alpha in WPiOS (like it was when I did my beta for WPAndroid) – which is why this hasn't triggered a merge conflict and why this bump can be merged as is in develop
Flagging @antonis @geriux just to check about the plan for the new 1.65.0-alpha* in WPiOS (ie either make it be cut from 1.64.1, or, more likely, include that fix from 1.64.1 in the new 1.65.0-alpha*, as you already did that for WPAndroid. Given the increase in Gutenberg versions in WPiOS's develop differed here from WPAndroid where we already had a new alpha in-between, just wanted to be sure.
I think it's all good because the upcoming 1.65.0-alpha2 you are working on, and likely plan to merge in WPiOS's develop (just like what you started in WPAndroid), is already supposed to include that same fix that was in 1.64.1 anyway (it's the same Gutenberg as WPAndroid after all)… but it doesn't hurt to ask confirmation and better safe than sorry 😄
There was a problem hiding this comment.
I'm surprised that develop is not yet on an v1.65.0-alpha in WPiOS (like it was when I did my beta for WPAndroid) – which is why this hasn't triggered a merge conflict and why this bump can be merged as is in develop.
Usually, alpha versions are merged when there are native changes that affect Gutenberg mobile, sometimes is for both platforms but in this case, it was only for Android because of new changes to react-native-aztec and S3.
It's all good because next week we will cut 1.65.0 to be merged in develop before the next release cut.
There was a problem hiding this comment.
Thanks for the confirmation. All good then 👍



No description provided.