The False Reporting of Releases

[shakey_snake]

Some threads like this one:

https://www.neowin.net/forum/index.php?show...=623547&hl=

Just flat out give misinformation. Could maybe the titles of thread like this be edited so that Neowin isn't a misinformation factory (ok, a bit of a stretch, but you know what I mean :p)?

Like the above thread is currently titled:

Firefox Beta 4 (Win)

but maybe it could be changed to:

Another Nightly build...

and then the topic description could be changed to:

was: "Firefox Beta 4 (Win)"

I believe that would at least that would cut down on the confusion for some people.

Edited March 4, 2008 by shakey_snake

[Joel]

Just write a program to make everyone smarter and less of a newshound. That will solve all of our issues. :p

[Steven P. Administrators]

If this had been on our news pages then yes, but seeing as BPN is a forum any member can post in, it goes without saying that not everything thats posted in there is going to be correct ;)

Common sense really.

[TheReaperMan]

Common sense really.

from some people?? never :p

[BinaryFragger]

It's not the first time a new Firefox release was falsely reported.

The issue was addressed by the Mozilla folks themselves last year.

[suicide_pact]

https://www.neowin.net/forum/index.php?show...#entry589256279

[drachma]

Some threads like this one:

https://www.neowin.net/forum/index.php?show...=623547&hl=

Just flat out give misinformation. Could maybe the titles of thread like this be edited so that Neowin isn't a misinformation factory (ok, a bit of a stretch, but you know what I mean :p)?

Like the above thread is currently titled:

Firefox Beta 4 (Win)

but maybe it could be changed to:

Another Nightly build...

and then the topic description could be changed to:

was: "Firefox Beta 4 (Win)"

I'm not going to belabor the point here but I just wanted to point out a build that is 'code freezed' for the actual release of ff3 beta 4. it's the exact same code that they'll be releasing (just not fully QA release checked).

it's not just a nightly.

when beta4 actually releases you can go ahead and compare the build versions and find it all identical.

whatever i'm done with this.

[shakey_snake]

Actually, since there have been two release candidates, what you linked to was not "exactly the same code".

What you linked to when you did was build number 2008303017 While RC2 is build 2008030714.

When they did QA they found that PGO wasn't turned on in all Windows builds. Why do you think they do Quality Assurance testing? Just to put a rubber stamp on things?

So, there is a lesson here for you, mate: don't announce builds until they've been officially announced.

Edited March 8, 2008 by shakey_snake