Closed
Bug 1137110
Opened 9 years ago
Closed 9 years ago
inspector rev in client.py is using the wrong rev in comm-beta
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(seamonkey2.34 fixed)
RESOLVED
FIXED
seamonkey2.34
Tracking | Status | |
---|---|---|
seamonkey2.34 | --- | fixed |
People
(Reporter: ewong, Assigned: ewong)
Details
Attachments
(1 file, 1 obsolete file)
1.12 KB,
patch
|
kairo
:
review+
kairo
:
approval-comm-beta+
|
Details | Diff | Splinter Review |
In comm-beta, client.py has: 27 # URL of the default hg repository to clone for DOM Inspector. 28 'INSPECTOR_REPO': 'https://hg.mozilla.org/dom-inspector/', 29 # The stable revision to use 30 'INSPECTOR_REV': 'DOMI_LATEST_RELEASE', This is not right since DOMI_LATEST_RELEASE has been updated to fix bug 1128291. Instead, c-b should (I believe) use 'SEA2_26_RELBRANCH' which doesn't have that change.
![]() |
Assignee | |
Comment 1•9 years ago
|
||
Attachment #8569712 -
Flags: review?(bugspam.Callek)
![]() |
Assignee | |
Comment 2•9 years ago
|
||
Comment on attachment 8569712 [details] [diff] [review] proposed patch (v1) [Approval Request Comment] Regression caused by (bug #): bug 1128291 User impact if declined: bustage Testing completed (on m-c, etc.): Risk to taking this patch (and alternatives if risky): String changes made by this patch:
Attachment #8569712 -
Flags: approval-comm-beta?
I think we will need to create a new branch. Probably from the DOMI_2_0_15 branch and based on http://hg.mozilla.org/dom-inspector/rev/6abb72a17277 as you probably need the compat vers changes.
![]() |
Assignee | |
Comment 4•9 years ago
|
||
(In reply to Ian Neal from comment #3) > I think we will need to create a new branch. Probably from the DOMI_2_0_15 > branch and based on http://hg.mozilla.org/dom-inspector/rev/6abb72a17277 as > you probably need the compat vers changes. Ratty suggested we use DOMI_2_0_15_1 as the tag. Should I go ahead and create that tag?
Flags: needinfo?(iann_bugzilla)
![]() |
Assignee | |
Updated•9 years ago
|
Attachment #8569712 -
Flags: review?(bugspam.Callek)
Attachment #8569712 -
Flags: approval-comm-beta?
(In reply to Edmund Wong (:ewong) from comment #4) > (In reply to Ian Neal from comment #3) > > I think we will need to create a new branch. Probably from the DOMI_2_0_15 > > branch and based on http://hg.mozilla.org/dom-inspector/rev/6abb72a17277 as > > you probably need the compat vers changes. > > Ratty suggested we use DOMI_2_0_15_1 as the tag. > > Should I go ahead and create that tag? That is fine by me, I was thinking SEA2_34_RELBRANCH but DOMI_2_0_15_1 seems okay too.
Flags: needinfo?(iann_bugzilla)
![]() |
Assignee | |
Comment 6•9 years ago
|
||
Using DOMi cset 60242bd0c895 (as tagged as DOMI_2_0_15_1)
Attachment #8569712 -
Attachment is obsolete: true
Attachment #8570344 -
Flags: review?(bugspam.Callek)
![]() |
Assignee | |
Updated•9 years ago
|
Attachment #8570344 -
Flags: review?(bugspam.Callek) → review?(Pidgeot18)
![]() |
||
Updated•9 years ago
|
Attachment #8570344 -
Flags: review?(Pidgeot18) → review+
![]() |
Assignee | |
Comment 7•9 years ago
|
||
Comment on attachment 8570344 [details] [diff] [review] proposed patch (v2) [Approval Request Comment] Regression caused by (bug #): 1128291 User impact if declined: bustage during osx64 build. Testing completed (on m-c, etc.): Risk to taking this patch (and alternatives if risky): String changes made by this patch:
Attachment #8570344 -
Flags: approval-comm-beta?
![]() |
||
Comment 8•9 years ago
|
||
Comment on attachment 8570344 [details] [diff] [review] proposed patch (v2) Review of attachment 8570344 [details] [diff] [review]: ----------------------------------------------------------------- Ah, sure, this is for beta, so I should have set this a+ right away :)
Attachment #8570344 -
Flags: approval-comm-beta? → approval-comm-beta+
![]() |
Assignee | |
Comment 9•9 years ago
|
||
Comment on attachment 8570344 [details] [diff] [review] proposed patch (v2) Pushed to comm-beta: https://hg.mozilla.org/releases/comm-beta/rev/8fc40ff84c71
![]() |
Assignee | |
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-seamonkey2.34:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.34
You need to log in
before you can comment on or make changes to this bug.
Description
•