Closed
Bug 507610
Opened 15 years ago
Closed 15 years ago
Please QA the Fujitsu-Siemens Partner Repack (3.5.2)
Categories
(Release Engineering :: Release Requests, defect)
Release Engineering
Release Requests
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: cbook, Assigned: kev)
Details
Starting the QA review process on the 3.5.2 version of the FujitsuSiemens partner distribution of Firefox. The repack worksheet is located at: https://wiki.mozilla.org/Partnering:Repacks:Firefox3:FujitsuSiemens Please note that the installers, until QA'd and digitally signed, are password protected. Distributions will be publicly available once they are QA'd and signed.
Reporter | ||
Comment 1•15 years ago
|
||
QA tests pass and requirements matched. Test results are here : https://wiki.mozilla.org/Partnering:Repacks:Firefox3:FujitsuSiemens:3.5.2 QA signs off --> back to Kev
Assignee: cbook → kev
Assignee | ||
Comment 2•15 years ago
|
||
Released to partner.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 3•15 years ago
|
||
(In reply to comment #0) > (...) > > Please note that the installers, until QA'd and digitally signed, are password > protected. Distributions will be publicly available once they are QA'd and > signed. Available where? I can't access https://people.mozilla.com/files/partners/fujistsusiemens/
Assignee | ||
Comment 4•15 years ago
|
||
Status pages and links need to be updated, and will be completed today. https://people.mozilla.com/files/partners/fujistsusiemens/3.5.2/ is where these repacks are hosted.
Assignee | ||
Comment 5•15 years ago
|
||
Something appears to have changed with the auth config on people, so these are password-protected but shouldn't be. Working on it.
Assignee | ||
Comment 6•15 years ago
|
||
Or, as Tomcat pointed out, I could try the correct URL :) https://people.mozilla.com/files/partners/fujitsusiemens/3.5.2/
Updated•11 years ago
|
Component: Release Engineering: Custom Builds → Release Engineering: Releases
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•