Closed
Bug 133797
Opened 22 years ago
Closed 22 years ago
Update the User Agent String for Mozilla 1.0 release
Categories
(SeaMonkey :: Build Config, defect, P1)
SeaMonkey
Build Config
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.0
People
(Reporter: lpham, Assigned: asasaki)
References
Details
Attachments
(3 files)
682 bytes,
patch
|
lpham
:
review+
leaf
:
superreview+
|
Details | Diff | Splinter Review |
671 bytes,
patch
|
lpham
:
review+
leaf
:
superreview+
|
Details | Diff | Splinter Review |
685 bytes,
patch
|
leaf
:
superreview+
leaf
:
approval+
|
Details | Diff | Splinter Review |
Need two patches to update the UserAgent string for Mozilla 1.0 release on the trunk and MOZILLA_1_0_0_BRANCH This bug must do after Mozilla 1.0 RC1 completes.
Changed the keyword to mozilla1.0 (requested by Asa) I want to make it clear for this bug. We need two patches for this bug. -Update UserAgent String on the trunk to 1.0.0+ -Update UserAgent String on MOZILLA_1_0_0_BRANCH to 1.0.0 *must do after releasing Mozilla 1.0 RC1
Keywords: nsbeta1+ → mozilla1.0
Assignee | ||
Updated•22 years ago
|
Status: NEW → ASSIGNED
Whiteboard: todo *after* beta release.
Updated•22 years ago
|
Whiteboard: todo *after* beta release. → todo *after* mozilla beta release.
Aki,there is some discussion about updating the UserAgent in bug #133794 patch id=78923 . I'm not sure they want to do it before RC1 or not. Please check the status of bug #133794 before working on this one. Thanks.
Assignee | ||
Comment 5•22 years ago
|
||
Assignee | ||
Comment 6•22 years ago
|
||
Assignee | ||
Updated•22 years ago
|
Whiteboard: todo *after* mozilla beta release. → need r/sr
Comment 7•22 years ago
|
||
Comment on attachment 81021 [details] [diff] [review] branch patch sr=leaf
Attachment #81021 -
Flags: superreview+
Leaf, Do we need to change to rc2 on the branch or just do 1.0.0?
Assignee | ||
Updated•22 years ago
|
Whiteboard: need r/sr → need r
Comment on attachment 81021 [details] [diff] [review] branch patch r=lpham Aki, don't worry about rc2 for now. We will have a different bug if we need for rc2.
Attachment #81021 -
Flags: review+
Comment 10•22 years ago
|
||
Comment on attachment 81022 [details] [diff] [review] trunk patch sorry, i was waiting for the 1.0.0 final release before super-reviewing this, but that's not what we usually do anyway. sr=leaf
Attachment #81022 -
Flags: superreview+
Reporter | ||
Comment 11•22 years ago
|
||
Comment on attachment 81022 [details] [diff] [review] trunk patch look good, r=lpham
Attachment #81022 -
Flags: review+
Assignee | ||
Comment 12•22 years ago
|
||
checked into branch and trunk.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Keywords: fixed1.0.0
Resolution: --- → FIXED
Whiteboard: need r
Comment 13•22 years ago
|
||
Sorry for dropping in so late, but I really think you should wait until the last moment with this change. Remember the incident where a German news site announced the release of RC 1 before it was released, simply because the about page said that what they had downloaded was RC 1? We wouldn't want a lot of "1.0 is here!!!" announcements tomorrow, would we? I strongly suggest you back out the branch patch.
Assignee | ||
Comment 14•22 years ago
|
||
branch changed to 1.0rc2. reopening since i'll have to checkin 1.0.0 change after rc2, close to 1.0 release.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•22 years ago
|
Keywords: fixed1.0.0
Reporter | ||
Comment 15•22 years ago
|
||
Thanks Aki for quick response and changing to rc2. Loan
Comment 16•22 years ago
|
||
Jonas: If you look at http://www.mozilla.org/roadmap.html, you'll see that around May 22 we will have mozilla1.1alpha on the trunk. At the time final mozilla1.0 may still be not released! Confusion is hard to avoid in the situation of branch heading for 1.0 final and trunk for 1.1alpha but this is no reason for calling the trunk 0.9.9+ _after_ 1.0 branched.
Assignee | ||
Comment 17•22 years ago
|
||
jacek: the trunk wasn't backed out, and it's at 1.0.0+ the change only occurred on the branch.
Comment 18•22 years ago
|
||
> Jonas: [...] this is no reason for calling the trunk 0.9.9+ _after_ 1.0 branched.
Agreed -- that's why I said "I strongly suggest you back out the *branch* patch"
(emphasis added) :-)
Assignee | ||
Comment 19•22 years ago
|
||
since I did actually update the UserAgent string on the trunk and branch after rc1, I'm going to call this one fixed and we can open a new bug for the actual release.
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 20•22 years ago
|
||
Aki, Please submit the patch to update UserAgent string for Mozilla 1.0 RC3. Thanks.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 21•22 years ago
|
||
Reporter | ||
Comment 22•22 years ago
|
||
Look good r=lpham
Comment 23•22 years ago
|
||
Comment on attachment 83614 [details] [diff] [review] rc3 branch patch amen, sr=leaf
Attachment #83614 -
Flags: superreview+
Attachment #83614 -
Flags: approval+
Assignee | ||
Comment 24•22 years ago
|
||
checked in. guessing we'll reopen for 1.0rtm/rc4/whatever.
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 25•22 years ago
|
||
Aki, you're right. Now is the time to submit the patch for Mozilla 1.0 release. Please try to complete it today so the build tomorrow will be Mozilla 1.0 Thanks.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 26•22 years ago
|
||
Aki already had the patch #81021 and got r= and sr=. Aki will check it in when the branch tree is open. Loan
Comment 27•22 years ago
|
||
The User Agent string was already updated yesterday by Leaf (see bonsai or <http://lxr.mozilla.org/mozilla1.0/source/modules/libpref/src/init/all.js#46>)
Reporter | ||
Comment 28•22 years ago
|
||
Yeah. Leaf is a head of me. Thanks for your info. I close the bug.
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•