Closed
Bug 1804359
Opened 2 years ago
Closed 2 years ago
Update uuid to 1.x
Categories
(Core :: General, task)
Core
General
Tracking
()
RESOLVED
FIXED
110 Branch
Tracking | Status | |
---|---|---|
firefox110 | --- | fixed |
People
(Reporter: glandium, Assigned: glandium)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
No description provided.
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Attachment #9306982 -
Attachment description: Bug 1804359 - Update uuid to 1.x. → Bug 1804359 - Update glean to 51.8.4 and uuid to 1.x.
Comment 2•2 years ago
|
||
We're gonna release a new major version, which will require minimal changes to FOG code. I can amend the patch once we have the release.
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Attachment #9306982 -
Attachment is obsolete: true
Assignee | ||
Comment 4•2 years ago
|
||
Since the glean update is stuck, let's go with uuid only.
Updated•2 years ago
|
Attachment #9306982 -
Attachment is obsolete: false
Updated•2 years ago
|
Attachment #9306982 -
Attachment description: Bug 1804359 - Update glean to 51.8.4 and uuid to 1.x. → Bug 1804359 - Update uuid to 1.x.
Pushed by mh@glandium.org:
https://hg.mozilla.org/integration/autoland/rev/9f1c75b155cc
Update uuid to 1.x. r=emilio,janerik,webdriver-reviewers,supply-chain-reviewers
Pushed by imoraru@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b7ad75f54047
fix for build bustages related to uuid. CLOSED TREE
Pushed by imoraru@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/af57073abd74
fix for build bustages related to uuid part 2. CLOSED TREE
Comment 8•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/9f1c75b155cc
https://hg.mozilla.org/mozilla-central/rev/b7ad75f54047
https://hg.mozilla.org/mozilla-central/rev/af57073abd74
Status: REOPENED → RESOLVED
Closed: 2 years ago → 2 years ago
status-firefox110:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•