Closed
Bug 1444922
Opened 7 years ago
Closed 7 years ago
Release geckodriver 0.20.1
Categories
(Testing :: geckodriver, enhancement, P1)
Testing
geckodriver
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ato, Assigned: ato)
References
Details
No description provided.
|
Assignee | |
Updated•7 years ago
|
|
|
Assignee | |
Comment 1•7 years ago
|
||
Ugh. I kind of botched the 0.20.0 release by including the patch
for bug 1444431, which should’ve made it into the 0.20.1 release.
Sorry about that. I had every intention of making a separate
release, but at some point there was a cognitive breakdown. I blame
the suboptimal release process.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
|
||
Comment 2•7 years ago
|
||
Can you explain how you was able to do that? Basically the 0.20 release should have happened based on the last changeset from bug
1401129 and not tip of central. Is that what happened to you? If yes we have to include that in our docs.
Flags: needinfo?(ato)
|
|
Assignee | |
Comment 3•7 years ago
|
||
Yes. 0.20.0 was released from fcebbde75cdf388d78b41d575d057fa4d3f90799
(HEAD of central at the time), whereas it should’ve been released
from 5a338157f989477a1b90c06c728926351ea455bd (bug 1401129).
I’ve updated the documentation in
https://bugzilla.mozilla.org/show_bug.cgi?id=1445244.
Flags: needinfo?(ato)
You need to log in
before you can comment on or make changes to this bug.
Description
•