1.3b yet?

[Joao M]

Well, from Asa's post, I'd say they should be the same thing.

The latest Phoenix nightly (20030104) still says 1.3a.

So does 20030105.

[daihard]

Well, from Asa's post, I'd say they should be the same thing.

The latest Phoenix nightly (20030104) still says 1.3a.

So does 20030105.

I guess this doesn't matter much as long as it works. I'm sure the Phoenix team will get on it once they get back on the project.

[aroben]

Oddly enough, in Windows XP Home Edition, in the "Version" tab under the file Properties, it gives both the "File Version" and the "Product Version" as 1.3b.

-Adam

[Jeff_pony]

Is the 'b' part of 1.3 changed by hand then or does this mean that pheonix is actually a revision behind? I guess this is something that isnt critical, else more of a stink would be made of it right?

[Kemayo]

Phoenix is built off the current Mozilla trunk, so it should always be based on the most up-to-date Mozilla code... I think it's just that they haven't gotten around to changing the revision number manually yet.

[Sipaq]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021218 Phoenix/0.5
^^^^^^^picked up from Mozilla^^^^^^^^|^^^buildID^^^|^set by us^

When Mozilla updates it's rv: then Phoenix will pick this up.

--Asa

Asa, the problem is, that Phoenix still reports 1.3a as its revision, when Mozilla itself already reports 1.3b. There is already a bug for this: <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=186680">bug 186680</a>. You even commented on it. It is currently assigned to Ben (it was assigned to Blake, but he isn't coding on Phoenix right now as far as I can see), but this patch is very easy to apply and also pretty straightforward, so you could check it in also if you dare

PS: I sent you an e-mail two weeks ago. Nothing happened. Anything wrong?

[alanjstr]

So the problem is that all.js was branched for Phoenix, so it doesn't actually pick up the name changes, even though it gets the date change.