1145796 - Make sure that push_apk.py doesn't remove Google play release notes

Status: RESOLVED WONTFIX

(Release Engineering :: Release Automation, defect)

Description

[Sylvestre Ledru [:Sylvestre]]

it seems that push_apk.sh is removing the release notes.
I should investigate why

Comment 1

[Sylvestre Ledru [:Sylvestre]]

What's new is attached to the apk:
https://support.google.com/googleplay/android-developer/answer/189724?hl=en
So, it is normal that updating it reset it.

The solution would be to get the "what's new" content during the beta cycle
https://developers.google.com/android-publisher/api-ref/edits/apklistings
and reuse it (ditto for release)

Comment 2

[Sylvestre Ledru [:Sylvestre]]

To sum up the issue, the "What's new" content is set by marketing and not release management.

So, we have to retrieve the previous "What's new" when we publish a new beta or release in the same cycle (for example, if we upload 38 beta 4 after 38 beta 2).
If we upload a new major release (ex: 37 after 36), in this case, we can drop the change notes.

The way Google play is managing apk is with versionCode (date + hour) and not versionName (ex: 38.0b2) and, at least for now, doesn't provide an way to retrieve the version.
Therefor, it is not yet possible to know when to keep the notes and when to update them... :/

I reported:
https://github.com/googlesamples/android-play-publisher-api/issues/18

Comment 3

[Sylvestre Ledru [:Sylvestre]]

Instead of waiting for Google to implement bug 18 (cf comment #2), Lawrence suggested that we instead extend nucleus to manage a specific field for the Google play release notes.
push_apk.py would query nucleus (example of URL https://nucleus.mozilla.org/rna/releases/?product=Firefox&version=38.0beta&format=json ), retrieve the notes and update them on Google play.

Comment 4

[Sylvestre Ledru [:Sylvestre]]

We are now doing what I mentioned in comment #3