Create and localize standard text for Fennec for the Play Store

RESOLVED FIXED in Firefox 62

Status

()

RESOLVED FIXED
6 months ago
2 months ago

People

(Reporter: lizzard, Assigned: delphine)

Tracking

Firefox 62
Firefox 62
Points:
---

Firefox Tracking Flags

(firefox62+ fixed)

Details

(Reporter)

Description

6 months ago
Rather than adding new "What's new" blurbs to the product in the Play Store with every release, we'd like to come up with a more general text that we can keep consistent across several releases. This would start for the Fennec 62 beta and continue to 62 release.

Suggested text:

We're always making Firefox on Android better. Each new release introduces new features, bug fixes, and performance improvements.

See https://www.mozilla.org/en-US/firefox/android/notes/ for the full list of changes for this release.
(Reporter)

Comment 1

6 months ago
Susheel, how does this sound to you? Please feel free to tweak the wording. 

Delphine, here's a bug which I'll keep tracked for 62 - hope this will give your team a little more time than usual to do the localization work, which then we won't have to keep repeating.
tracking-firefox62: --- → +
Flags: needinfo?(sdaswani)
Flags: needinfo?(lebedel.delphine)
+Michelle
Flags: needinfo?(mheubusch)
One side though: there was work recently (bug 1459181) done on mozapkpublisher to fetch version XX of whatsnew content.

Our webapp provides WN content in two ways:
a) Asking for a specific version, e.g. https://l10n.mozilla-community.org/stores_l10n/api/v1/fx_android/translation/60/fr/
b) Asking for a channel, e.g. https://l10n.mozilla-community.org/stores_l10n/api/v1/fx_android/translation/release/fr/ (with other data)

Version XX (a) can be provided only if we have files for version XX, which is not going to be the case. So, this would also require changes to mozapkpublisher.

Comment 4

6 months ago
My recommendation (since not every release has a new feature)

We're working to make Firefox for Android better with each new release. Read the release notes to learn about any new features, bug fixes, and performance improvements at https://www.mozilla.org/en-US/firefox/android/notes/.
Flags: needinfo?(mheubusch)
Adding jlorenzo so he can look into comment 3.
Flags: needinfo?(lebedel.delphine)
(In reply to Francesco Lodolo [:flod] from comment #3)
Worst case scenario, mozapkpublisher can keep downloading the what's new string, but not craft the request to change it. That's what we do in Nightly, for instance[1]

[1] https://github.com/mozilla-releng/mozapkpublisher/blob/master/mozapkpublisher/push_apk.py#L113-L116
(In reply to Johan Lorenzo [:jlorenzo] from comment #6)
> (In reply to Francesco Lodolo [:flod] from comment #3)
> Worst case scenario, mozapkpublisher can keep downloading the what's new
> string, but not craft the request to change it. That's what we do in
> Nightly, for instance[1]

I don't think that's an option, if we want to change the current strings to the new text, and pick up new languages if they're added in the future?
We can just update them every time.
Google play is smart enough to drop unchanged strings!
(In reply to mheubusch from comment #4)
> My recommendation (since not every release has a new feature)
> 
> We're working to make Firefox for Android better with each new release. Read
> the release notes to learn about any new features, bug fixes, and
> performance improvements at
> https://www.mozilla.org/en-US/firefox/android/notes/.

Ship it! :)
Flags: needinfo?(sdaswani)
(In reply to mheubusch from comment #4)
> My recommendation (since not every release has a new feature)
> 
> We're working to make Firefox for Android better with each new release. Read
> the release notes to learn about any new features, bug fixes, and
> performance improvements at
> https://www.mozilla.org/en-US/firefox/android/notes/.

Just to be sure, I should update beta and release with this generic text in time for next merge day correct?
Or did you want this text to be updated now already? (not sure who's call it is :) )
Flags: needinfo?(lhenry)
(Reporter)

Comment 11

6 months ago
It would be great if we can do this in time for the 62.0b1 release (aiming for that release to be June 19th)
Flags: needinfo?(lhenry)
Gotcha! Definitely can help out with that
This has been taken care of. Thanks all!
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → FIXED
Assignee: nobody → lebedel.delphine
status-firefox62: affected → fixed
Target Milestone: --- → Firefox 62
Blocks: 1496090
You need to log in before you can comment on or make changes to this bug.