Closed Bug 1494393 Opened 6 years ago Closed 6 years ago

Upload a beta version of Send Android to the play store for testing by an audience of mozillians

Categories

(Release Engineering :: Release Requests, enhancement)

Unspecified
Android
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1534348

People

(Reporter: fzzzy, Unassigned)

Details

Attachments

(2 files, 8 obsolete files)

Attached file app-debug.apk (obsolete) —
Hello, We would like to begin testing an early version of the Send Android app, which is scheduled for a full release in Q1 next year. This version is still very rough, but I have little experience with Android so I would like to learn about the process sooner than later. I have created an apk but I don't think it is signed. Let me know if there is something extra I need to do there. I used bug 1474328 as a reference when creating this bug. Let me know if I filled out anything incorrectly.
Does this need to be published in the play store for initial testing? Could our test audience install the APK manually instead?
(In reply to Chris AtLee [:catlee] from comment #1) > Does this need to be published in the play store for initial testing? Could > our test audience install the APK manually instead? Our q4 goal is to have 50 mozillians test the beta. So far, I have asked people to install the APK manually but as far as I know, zero mozillians have done so. I think using whatever process notes used for a beta would really help us to meet our quarterly goal. Since this is a short quarter, I'd like to get started as soon as possible.
Is your intent to have the full release use the same application id as this early test app, or are you planning on having early adopters re-install a new app after some initial testing?
Attached file Send Android Beta Version (obsolete) —
Attachment #9012291 - Attachment is obsolete: true
(In reply to Chris AtLee [:catlee] from comment #3) > Is your intent to have the full release use the same application id as this > early test app, or are you planning on having early adopters re-install a > new app after some initial testing? There is a new beta version, which is feature complete but has a few known bugs. It would be nice to make this available for testing by mozillians soon. The beta uses a non-production fxa server. Going forward, there will likely continue to be a beta version for testing purposes. Therefore, early adopters should re-install the final version which uses the production fxa once it is available. The current plan is to have the production version ready in January. Shall I give this beta version a different app id? What app id shall I give it? Thanks.
If you intend to have beta users get updated to the final version later, then you can use the same app id. If you want to keep separate beta / release tracks going in parallel, then you need separate app ids. What is the app id right now?
(In reply to Chris AtLee [:catlee] from comment #6) > If you intend to have beta users get updated to the final version later, > then you can use the same app id. > > If you want to keep separate beta / release tracks going in parallel, then > you need separate app ids. > > What is the app id right now? I think it would be good to have beta / release tracks, so that one uses the non-production fxa and one uses the production one. So I'll make separate app ids. The app id right now is 'com.mozilla.send.sendandroid'. Do I really have to rename the main package to change the app id?
Summary: Upload a very early version of Send Android to the play store for testing by a small internal audience of mozillians → Upload a beta version of Send Android to the play store for testing by an audience of mozillians
Sylvestre, Devin said to needinfo you on this bug in case you have opinions.
Flags: needinfo?(sledru)
I would prefer org.mozilla to be consistent with the rest of our android app. For the rest, I don't have a strong opinion (just confused to see 'send' duplicated)
Flags: needinfo?(sledru)
By the way, when you are ready, here is the list of expectations that we have: https://wiki.mozilla.org/Release_Management/Adding_a_new_app_on_Google_play
Attachment #9026454 - Attachment is obsolete: true
:sylvestre thank you very much. I have renamed the package to org.mozilla.sendandroid. Also, after further discussion with the Send team, we determined that there is no need to have a separate beta app. Thus, I have switched the latest apk to use the production fxa server. When the beta period is over, the release version will continue to have the same app id and package name.
Attachment #9027980 - Attachment is obsolete: true

Many features and bugfixes. Close to ready for release.

Attachment #9028929 - Attachment is obsolete: true
Attached image beta-icon.png

App icon for the beta app

We're ready to go with the closed beta release of Firefox Send. We can use the latest APK, and attached app icon. Attached is a list of GPS email addresses for the beta testing audience:

https://docs.google.com/spreadsheets/d/1X_PJ7knRxnqT72ivK-QCLuJUsK4nNLmQaIj9zee19A4/edit#gid=0

I've also attached a temporary app icon while we finalize assets for a real release...

Sylvestre, on the relman wiki you say "an APK, please note that the APK name org.mozilla.foo.bar will remain the same forever"...should we change the name of the attached APK to something more generic before we release the closed beta?

Additionally, I'm fine using lorem ipsum placeholder text for GPS descriptions while in Beta. Do you need placeholder images now, or can i wait until we have the real ones?

Flags: needinfo?(sledru)
Attached file Latest build from 2019-2-11 (obsolete) —
Attachment #9041798 - Attachment is obsolete: true
Attached file Build 2019-02-19 (obsolete) —
Attachment #9043617 - Attachment is obsolete: true

Could you please upload an apk without debug info?
You uploaded a debuggable APK or Android App Bundle. For security reasons you need to disable debugging before it can be published in Google Play.

Flags: needinfo?(sledru) → needinfo?(dpreston)

Here's the release build.

Attachment #9045067 - Attachment is obsolete: true
Flags: needinfo?(dpreston)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: