Closed
Bug 443240
Opened 18 years ago
Closed 18 years ago
Why is there partner stuff on releases.mozilla.org instead of releases.mozilla.com?
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 428080
People
(Reporter: reed, Unassigned)
References
()
Details
While looking into another issue, I happened to notice partner stuff on releases.mozilla.org. I thought we created releases.mozilla.com for the explicit purpose of serving partner stuff, so I was wondering why there was partner stuff on releases.mozilla.org (http://releases.mozilla.org/pub/mozilla.org/firefox/releases/partners/). I don't think we should be asking our mirrors to host partner-specific stuff for us when we already have another place for things like that...
Marking this as mozillacomconfidential for now since it regards partners, but it could probably be opened...
Comment 1•18 years ago
|
||
Similar to bug 428080, the full installers should not be shipped out. The mars should be, if there's any chance of a MU request for partner builds going to those mirrors. I believe we can safely remove the full installers, but would not be comfortable removing the .mar files prior to auditing bouncer configs, etc.
Also marking public, as they're all released packages.
Group: mozillacomconfidential
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•