Closed Bug 507608 Opened 16 years ago Closed 16 years ago

Please QA and Sign the T-Online Partner Repack (3.5.2)

Categories

(Release Engineering :: Release Requests, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cbook, Assigned: kev)

Details

Starting the QA review process on the 3.5.2 version of the T-Online partner distribution of Firefox. The repack worksheet is located at: https://wiki.mozilla.org/Partnering:Repacks:Firefox3:T-Online 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.
QA tests passed and requirements matched. Testresults are here https://wiki.mozilla.org/Partnering:Repacks:Firefox3:T-Online:352 and QA signs off this Release. -> back to Kev
Assignee: cbook → kev
please sign the win32 installers per process. tarball of installers ready for signing on people at: people.mozilla.com:/tmp/tonline-352-unsigned.tar md5sum of the tarball is 2f65019b9de9107c178cdb9a643bacd7 --> over to releng
Assignee: kev → nobody
Assignee: nobody → bhearsum
Status: NEW → ASSIGNED
now signed at people.mozilla.org:/tmp/tonline-352-signed.tar md5sum is bf437b141b20fb091be4105c4350a12a
Assignee: bhearsum → nobody
These are all signed now AFAICT.
Assignee: nobody → kev
released to partner. thanks folks!
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
(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. I still can't access https://people.mozilla.com/files/partners/t-online/3.5/ (URL from bug 501473).
Status pages and links need to be updated, and will be completed today. https://people.mozilla.com/files/partners/t-online/3.5.2/ is where these repacks are hosted.
Component: Release Engineering: Custom Builds → Release Engineering: Releases
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.