Closed
Bug 1231679
Opened 10 years ago
Closed 10 years ago
Partner repack changes for Firefox 43
Categories
(Release Engineering :: Release Requests, defect)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Assigned: coop)
Details
Attachments
(2 files)
As we inch toward (re)automation, there are a bunch of changes required to manifests, repack scripts, and individual partner configs to get us there.
|
Assignee | |
Updated•10 years ago
|
Assignee: nobody → coop
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 1•10 years ago
|
||
Attachment #8697277 -
Flags: review?(nthomas)
|
|
Assignee | |
Comment 2•10 years ago
|
||
Attachment #8697279 -
Flags: review?(nthomas)
|
||
Updated•10 years ago
|
Attachment #8697279 -
Flags: review?(nthomas) → review+
|
|
||
Comment 3•10 years ago
|
||
Comment on attachment 8697277 [details] [review]
Add sha2signcode to list of signing formats; increase token duration
https://github.com/mozilla-partners/repack-scripts/pull/4/files changed the script, so at this point we're signing 43.0 repacks with sha2 and vanilla with sha1. Not sure how I feel about that.
Attachment #8697277 -
Flags: review?(nthomas) → review+
|
|
Assignee | |
Comment 4•10 years ago
|
||
Changes have been merged in github.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
||
Updated•4 years ago
|
Component: Custom Release Requests → Release Requests
You need to log in
before you can comment on or make changes to this bug.
Description
•