Closed
Bug 114686
Opened 24 years ago
Closed 24 years ago
update user agent for 0.9.7
Categories
(SeaMonkey :: Build Config, defect, P1)
SeaMonkey
Build Config
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.7
People
(Reporter: granrosebugs, Assigned: jj.enser)
References
()
Details
Attachments
(2 files)
|
773 bytes,
patch
|
leaf
:
review+
granrosebugs
:
superreview+
granrosebugs
:
approval+
|
Details | Diff | Splinter Review |
|
772 bytes,
patch
|
leaf
:
review+
granrosebugs
:
superreview+
granrosebugs
:
approval+
|
Details | Diff | Splinter Review |
Once the 0.9.7 branch is cut, we have to update the user agent.
On the 0.9.7 branch it should be "0.9.7"
On the trunk post-branch it should be "0.9.7+"
This bug covers both checkins and should have two patches landed before being
closed.
| Reporter | ||
Updated•24 years ago
|
Severity: normal → blocker
Priority: -- → P1
Target Milestone: --- → mozilla0.9.7
| Assignee | ||
Comment 2•24 years ago
|
||
| Assignee | ||
Comment 3•24 years ago
|
||
need r=/sr= on both patches to all.js
| Reporter | ||
Updated•24 years ago
|
Attachment #62047 -
Flags: superreview+
Attachment #62047 -
Flags: approval+
| Reporter | ||
Updated•24 years ago
|
Attachment #62048 -
Flags: superreview+
Attachment #62048 -
Flags: approval+
| Reporter | ||
Comment 4•24 years ago
|
||
sr=granrose for both patches, pending r=.
leaf - can you review these?
Comment 5•24 years ago
|
||
Comment on attachment 62047 [details] [diff] [review]
updating user agent to 0.9.7+ on the trunk
fabulous. r=leaf
Attachment #62047 -
Flags: review+
Comment 6•24 years ago
|
||
Comment on attachment 62048 [details] [diff] [review]
update user agent to 0.9.7 on the 0.9.7 branch
also fabulous. r=leaf
Attachment #62048 -
Flags: review+
| Assignee | ||
Comment 7•24 years ago
|
||
both patches checked in
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 8•24 years ago
|
||
*** Bug 116293 has been marked as a duplicate of this bug. ***
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•