Closed Bug 266199 Opened 20 years ago Closed 20 years ago

Figure out User-Agent string's rv: version for Firefox 1.0 release

Categories

(Firefox :: General, defect)

1.0 Branch
defect
Not set
blocker

Tracking

()

VERIFIED FIXED

People

(Reporter: marcia, Assigned: dbaron)

Details

(Keywords: fixed-aviary1.0, fixed1.7.5)

Attachments

(1 file)

As discussed at today's Aviary meeting. Will be discussed next week.
Flags: blocking-aviary1.0+
What is "RV"?
I guess they're going to paint an RV in pice pretty FireFox colors and drive it
around picking up chicks... or something. ;-P
http://www.google.com/search?q=define%3Arv

I go for the "ICBM Re-entry Vehicle containing the nuclear warhead(s). " Since
it best fits the bang" 

(however checking bugzilla shows that rv mostly stands for Return value. Note
that this is a Macos X bug) 
(In reply to comment #3)
> (however checking bugzilla shows that rv mostly stands for Return value. Note
> that this is a Macos X bug) 

I'm no bugzilla genious, but isn't that what the blocking-aviary1.0mac flag is for?
(In reply to comment #4)
(In reply to comment #3)
(In reply to comment #2)

I'm no genius either, but it doesn't take much to see that not one of these
comments was useful either for the developers or the people cc'd to this bug. 
Please don't add comments if your comment doesn't add to this bug in some
meaningful way.
Whiteboard: See comment 5 before commenting
Yeah, like this one? https://bugzilla.mozilla.org/show_bug.cgi?id=122411

(Maybe the RV needs a kitchen sink.)
(In reply to comment #5)
> (In reply to comment #4)
> (In reply to comment #3)
> (In reply to comment #2)
> 
> I'm no genius either, but it doesn't take much to see that not one of these
> comments was useful either for the developers or the people cc'd to this bug. 
> Please don't add comments if your comment doesn't add to this bug in some
> meaningful way.

Maybe these comments could have been avoided if the original poster of the bug
would have given some real information about the bug instead of simply writing
"as discussed...". 
Summary: Figure out RV for Firefox 1.0 release → Figure out User-Agent string's rv: version for Firefox 1.0 release
For those of you who do not know, the rv: string is the version number of the
equivalent Mozilla release that would have been built from the source code used
to build any version of Firefox with the matching rv:.

For example: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041030
Firefox/1.0RC2 (daihard: P4/SSE2) indicates that if the same source used to
build this nightly were used to build Mozilla, you would get Mozilla v1.7.3.

Will the rv: be in thw 1.7.X group?
Well, in my opionon it is a bit late in the game to be changing this now.  I
would think a change in the UI rv would be kind of a risky change.  For example,
if it is decided to change it to be the firefox version and change it to version
1.0, then a bunch of browser version sniffing JavaScript code is going to decide
the browser is Mozilla Version 1.0 which the site does not support and all of a
sudden there will be sites all over the Internet that worked just fine with the
PR realese and RC1that suddenly start telling everyone that their browser is too
old and they need to get a new one.
I don't think it's risky to change 1.7.3 to 1.7.5, which is the most likely choice.
re comment #10 I don't see that as being any risk.  That has certainly been done
before.  Just seeing we are going to change it and there was discussion just
made me fear it was going to be the firefox version rather than the core code
version which would make it go to 1.0 which I was pretty sure would break thinhgs.
I think the consensus we were leaning towards when this was last discussed was
to use 1.7.5 for the following reasons:
 * it leaves room for a 1.7.4 security release based on 1.7.3 if we need to do one
 * if we don't have a 1.7.4 security release, it indicates that it's a little
more than a normal dot release for when we do a MOZILLA_1_7_BRANCH-based release
that's Gecko-equivalent to the Aviary 1.0 releases.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
No aviary checkin yet. Reopening.
Status: RESOLVED → REOPENED
Keywords: fixed-aviary1.0
Resolution: FIXED → ---
Whiteboard: See comment 5 before commenting
Oops, sorry.
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Keywords: fixed-aviary1.0
Resolution: --- → FIXED
rv: 1.7.5 in today's firefox aviary1.0 build (2004110309-0.11, linux fc2).
vrfy'ing fixed.
Status: RESOLVED → VERIFIED
OS: MacOS X → All
Version: unspecified → 1.0 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: