1437611 - [Fx Acquisition] /new variation to support partner relationship

Status: NEW

(www.mozilla.org :: Pages & Content, enhancement)

Description

[Eric Renaud [:erenaud]]

Create variation of /new page to support relationship with Yandex

Comment 1

[Eric Renaud [:erenaud]]

project doc - https://docs.google.com/document/d/1HmWoIXaJww5Bge03GegjiutGJ3p7-u9tnw1-gcZHTYc/edit#

Comment 2

[Eric Renaud [:erenaud]]

Mike - please provide the download links for all the platforms on which the Yandex flavored version of Firefox

Comment 3

[Mike Kaply [:mkaply]]

> Mike - please provide the download links for all the platforms on which the Yandex flavored version of Firefox

So we don't actually host the Yandex builds of Firefox. They go into an s3 bucket and Yandex downloads them.

So I'm not sure what the right thing to do is here.

nthomas: Any thoughts here? Can we speciy for something to go in the s3 bucket for download and on our servers?

Would it be weird to direct downloads to the candidates URLs (which is where our partner builds live?)

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

Is there a reason the partner wouldn't continue to host downloads ? Not sure if you're saying we want to bring that in house. 

If we do want to host then https://archive.mozilla.org/pub/firefox/releases/partners/ would be preferable to a candidates directory, then set up download.m.o products and serve that via our CDNs as normal. We would need to augment the release automation if this is more than a short-term test. FYI, we don't currently publish that partner into candidates.

Comment 5

[Mike Kaply [:mkaply]]

> Is there a reason the partner wouldn't continue to host downloads ? Not sure if you're saying we want to bring that in house. 

That's the plan. I honestly don't even know where Yandex hosts these downloads.

> If we do want to host then https://archive.mozilla.org/pub/firefox/releases/partners/ would be preferable to a candidates directory, then set up download.m.o products and serve that via our CDNs as normal. We would need to augment the release automation if this is more than a short-term test. FYI, we don't currently publish that partner into candidates.

Those builds in that releases directory are quite old :).

Any idea what I could put in my repack.cfg to put files there?

I only have the configs from funnelcakes:



# Upload params
s3cfg=~/.s3cfg-mozilla
bucket="net-mozaws-prod-delivery-firefox"
upload_to_candidates=true
# NB: increment the .../vN/... for each configuration iteration,
# to avoid caching issues on archive.m.o
output_dir="partner-repacks/%(partner_distro)s/v5/%(platform)s/%(locale)s"

Comment 6

[Jonathan Petto [:jpetto]]

It looks like we're already going this route, but just want to say that we shouldn't be serving product downloads from third-party URLs/servers.

Comment 7

[Nick Thomas [:nthomas] (UTC+12)]

(In reply to Mike Kaply [:mkaply] from comment #5)
> Any idea what I could put in my repack.cfg to put files there?

That would be wrong place, even if it were possible to put something there, as we would end up publishing a new release for the partner before the vanilla builds.

I suggest building out the release automation to copy files from firefox/candidates into firefox/partners/, and make updates to bouncer a couple of times (setup a product, and point an alias at it later). If we did all that the url could be 
  https://download.mozilla.org/?product=firefox-latest-yandex-ssl&os=win64&lang=ru
with variations for product/langs that we're going to support.

Could someone let me know timeline and estimated longevity for this work by whatever appropriate means, and I'll set up the RelEng bugs.