352431 - Version bump for 2.0rc1

Status: RESOLVED FIXED

(Firefox :: General, defect)

Description

[J. Paul Reed [:preed]]

For the upcoming RC1, we need to bump the version number, check official branding, and make sure all the build infrastructure is pulling the right versions (l10n, AUS, AMO, etc.)

Unless someone else wants to, build/release can take care of the bump + the associated verification to make sure the bump propagates through the build system correctly.

I can take it for now, but if someone else needs to check something/do this, feel free to re-assign.

Comment 1

[Mike Connor [:mconnor]]

We should be able to just go ahead and change this whenever you have cycles.

Comment 2

[J. Paul Reed [:preed]]

Attachment: Bump version for rc1

Comment 3

[Mike Connor [:mconnor]]

Comment on attachment 238305 [details] [diff] [review]
Bump version for rc1

a=mconnor on behalf of drivers for 1.8 branch checkin

Comment 4

[J. Paul Reed [:preed]]

Checked in.

Comment 5

[pal-moz]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b2) Gecko/20060914 BonEcho/2.0 ID:2006091402

rv in UA is still "1.8.1b2".

Comment 6

[Jay Patel [:jay]]

I just updated to today's nightly builds, and the user-agent looks ok to me:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1) Gecko/20060914 BonEcho/2.0

However, the application is still "BonEcho"... do we want to make that "Firefox" yet?  Since the app version is now 2.0 (since we're at rc1), just want to make sure we don't miss anything.

Comment 7

[J. Paul Reed [:preed]]

(In reply to comment #6)

> However, the application is still "BonEcho"... do we want to make that
> "Firefox" yet?  Since the app version is now 2.0 (since we're at rc1), just
> want to make sure we don't miss anything.

I'll let mconnor confirm, but I think we will want to change this to Firefox when we're code complete, since the release should have Firefox/2.0 at the end of the user agent. I think?

I can whip up a patch for it.

Comment 8

[Mike Schroepfer]

Is this part of official branding switches?  If so we want to only flip it for those...

(In reply to comment #7)
> (In reply to comment #6)
> 
> > However, the application is still "BonEcho"... do we want to make that
> > "Firefox" yet?  Since the app version is now 2.0 (since we're at rc1), just
> > want to make sure we don't miss anything.
> 
> I'll let mconnor confirm, but I think we will want to change this to Firefox
> when we're code complete, since the release should have Firefox/2.0 at the end
> of the user agent. I think?
> 
> I can whip up a patch for it.
> 

Comment 9

[J. Paul Reed [:preed]]

(In reply to comment #8)
> Is this part of official branding switches?  If so we want to only flip it for
> those...

Looks like it might be. I didn't look closely enough at configure.in.

I'll confirm with :rs.

Comment 10

[Robert Strong (they/them - no direct email)]

-enable-official-branding should be all that is needed to change Bon Echo to Firefox, etc. One easy way to check is if the icon isn't the official icon.

Comment 11

[J. Paul Reed [:preed]]

Looks like this was fixed after all; reclosing.