Project-Branch `Date` should build fennec nightly with alternate branding to allow sideloading

RESOLVED FIXED

Status

()

Firefox for Android
Build Config & IDE Support
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: Callek, Assigned: Callek)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

MozReview Requests

()

Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:

Attachments

(1 attachment)

(Assignee)

Description

2 years ago
On the `Date` Project branch we are working on generating Android Nightlies in taskcluster.

To facilitate early testing we should change the android package name to something unique so it doesn't conflict with actual Fennec nightlies. Especially since early on we will be using a different signing certificate than the official nightly one (making installing this harder and potentially profile-losing)
Comment hidden (mozreview-request)

Comment 2

2 years ago
mozreview-review
Comment on attachment 8798393 [details]
Bug 1308170 - Project-Branch `Date` should build fennec nightly with alternate branding to allow sideloading.

https://reviewboard.mozilla.org/r/83908/#review82452

Looks fine to me :). Do you normally need review for landing test stuff on project branches? I thought you could commit whatever and only needed to get review for landing things on central.
Attachment #8798393 - Flags: review?(mshal) → review+
(Assignee)

Comment 3

2 years ago
(In reply to Michael Shal [:mshal] from comment #2)
> Comment on attachment 8798393 [details]
> Bug 1308170 - Project-Branch `Date` should build fennec nightly with
> alternate branding to allow sideloading.
> 
> https://reviewboard.mozilla.org/r/83908/#review82452
> 
> Looks fine to me :). Do you normally need review for landing test stuff on
> project branches? I thought you could commit whatever and only needed to get
> review for landing things on central.

We don't actually need review for `Date` and every project branch gets to define its own rules.

We do however want constantly useable code on date (rather than iterative patches that could break thing)

So I was asking review mainly as a "is this the right way to do what I'm suggesting" which I thought was right to begin with, but didn't hurt for confirmation.

https://hg.mozilla.org/projects/date/rev/61aaa8c13adbf5fd5e6ec0b09791be07a677a3d8
(Assignee)

Updated

2 years ago
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.