Firefox 3 final release in 2007?
beel...@gmail.com
only a short question:
Does someone of you actually believe that it is possible to release
the final version of Firefox 3 in 2007?
I ask because I have read in http://wiki.mozilla.org/ReleaseRoadmap
that you possibly want to release it in "Late 2007". But I can see
here, that you are going to release Beta 2 after some Beta2 RCs are
tested on 14th December: "Firefox 3 Beta2 Testday", then you want to
release Beta 3 and possibly some more Betas, and after the Betas there
will be some RCs for the final version I think. So I don't see any
chance that the final version of Firefox 3 will be released in 2007.
Regards
Beel
Dave Townsend
In general all dates on roadmap style pages are preliminary and often
towards the end of development cycles updating the roadmaps becomes less
important than the actual work on the product.
Of course the page you reference actually says "Late 2007 / Early 2008
(TBD): Firefox 3 released" so there was no hard and fast suggestion of
Late 2007 as being the target.
Dave
beel...@gmail.com
> In general all dates on roadmap style pages are preliminary and often
> towards the end of development cycles updating the roadmaps becomes less
> important than the actual work on the product.
OK, I know, because modification to the wiki-page was made on Nov/8
http://wiki.mozilla.org/index.php?title=ReleaseRoadmap&diff=40589&oldid=33755
but I wanted to get an statement from mozilla developers, that it is
definitely not possible to release the final in 2007
> Of course the page you reference actually says "Late 2007 / Early 2008
> (TBD): Firefox 3 released" so there was no hard and fast suggestion of
> Late 2007 as being the target.
Can I understand your answer as: _No, it is not possible to release in
2007_?
Regards
Beel
Robert Kaiser
> Dave:
>> Of course the page you reference actually says "Late 2007 / Early 2008
>> (TBD): Firefox 3 released" so there was no hard and fast suggestion of
>> Late 2007 as being the target.
>
> Can I understand your answer as: _No, it is not possible to release in
> 2007_?
Everything is possible in theory, but I'd say it's very improbable.
I'd expect to see Firefox 3 in Q1 of 2008, but it should actually be
done on a "when it's ready" basis - it's better to fix more important
bugs than to rush out a release that is not well-baked, esp. with a
multi-million user base such as Firefox has it.
Robert Kaiser
beel...@gmail.com
> Everything is possible in theory, but I'd say it's very improbable.
Danke schön Robert,
mehr wollte ich gar nicht, einfach nur ein Statement, schwarz auf weiß
mfg
Beel
Colin Barrett
My german is poor, but I believe beel...@gmail.com said something
along the lines of "Thank you, Robert, all I wanted was a yes or no."
-Colin
p.s. I was a little annoyed that you switched to German in the middle of
a conversation involving a number of other English speakers without
providing a translation.
Gijs Kruitbosch
Not quite. "schwarz auf weiss" literally means "black on white" and is
an expression perhaps similar to "having something in print", ie
something that you could use for journalism (quoting X on saying Y), for
a contract or for a legal debate.
Which leads me to something I was considering posting anyway: Robert is
not the best person to quote about Firefox stuff. In fact, if you were
looking for a quote, you should probably have asked Mozilla PR (or at
least someone@mozilla, where "someone" would probably be "staff" or
"press" or something) rather than dumping it in a newsgroup and hoping
the reply would be representable - which in this case it wasn't really.
Robert's a good guy, but last I checked he was more into SeaMonkey
development than Firefox :-).
That said, I agree with Robert - but then again, I'm not intimately
involved so quoting me would be a worse idea still.
~ Gijs
Mike Beltzner
> Which leads me to something I was considering posting anyway: Robert is
> not the best person to quote about Firefox stuff. In fact, if you were
> looking for a quote, you should probably have asked Mozilla PR (or at
> least someone@mozilla, where "someone" would probably be "staff" or
> "press" or something) rather than dumping it in a newsgroup and hoping
> the reply would be representable - which in this case it wasn't really.
> Robert's a good guy, but last I checked he was more into SeaMonkey
> development than Firefox :-).
The right address to use for press inquiries is pr...@mozilla.com -
they're quite responsive. :) That's if you want a direct, attributable
quote. Anything else would have to be you pointing to a newsgroup
posting; we have to deal with this all the time. We're an open,
community project, so you're gonna get a plurality of opinions and
"clarity" will be a best approximation.
> That said, I agree with Robert - but then again, I'm not intimately
> involved so quoting me would be a worse idea still.
I'm intimately involved and I'm pretty comfortable in saying that there
is no chance whatsoever that we'll see a Firefox 3 final release in
2007; we will, however, see a kickass Firefox 3 Beta 2 a little later
this month. :)
cheers,
mike
Mark Banner
> is no chance whatsoever that we'll see a Firefox 3 final release in
> 2007; we will, however, see a kickass Firefox 3 Beta 2 a little later
> this month. :)
Fair enough, but how about a little bit more on info on the next beta?
For instance I looked a few hours ago and I saw nothing on the wiki,
calendar (linked from the wiki) or planet about the when the next
freeze/beta is.
I've just found from today's meeting notes
(http://wiki.mozilla.org/Firefox3/StatusMeetings/2007-12-11) that the
next freeze is proposed on 22nd January.
So is that a feature-complete beta, or is there expected to be another
beta after that? When is l10n expected to freeze?
Whilst I realise that it can be hard to tell, could we please have just
a little bit more information even if its just "we expect 2 more betas
and after the first we'll be feature complete and interface frozen" or
something like that?
For developers working on SeaMonkey and Thunderbird its useful to know
timescales for when we need to get bugs/patches in and reviews for
achieving getting our fixes in Gecko 1.9 that we're probably going to be
doing our next release on.
Also whilst I'm here, as the roadmap page indicates a 1.9.1 branch, will
that be an interface freeze similar to the current 1.8(.1) branch?
Standard8
Mike Shaver
<bugz...@invalid.standard8.plus.com> wrote:
> I've just found from today's meeting notes
> (http://wiki.mozilla.org/Firefox3/StatusMeetings/2007-12-11) that the
> next freeze is proposed on 22nd January.
>
> So is that a feature-complete beta, or is there expected to be another
> beta after that? When is l10n expected to freeze?
>
> Whilst I realise that it can be hard to tell, could we please have just
> a little bit more information even if its just "we expect 2 more betas
> and after the first we'll be feature complete and interface frozen" or
> something like that?
As schrep has said before, we'll keep having betas until we don't
think we need any more of them. We don't have a fixed "beta budget",
though we care about making this work available to users in a timely
way of course!
> For developers working on SeaMonkey and Thunderbird its useful to know
> timescales for when we need to get bugs/patches in and reviews for
> achieving getting our fixes in Gecko 1.9 that we're probably going to be
> doing our next release on.
ASAP. Gecko 1.9 is already feature-frozen, as I understand it (which
happens prior to Firefox being feature-frozen, perhaps obviously).
> Also whilst I'm here, as the roadmap page indicates a 1.9.1 branch, will
> that be an interface freeze similar to the current 1.8(.1) branch?
I don't think that's been decided, though we prefer to preserve
compatibility where the cost of doing so isn't unreasonably high.
Mike
Colin Barrett
> For developers working on SeaMonkey and Thunderbird its useful to know
> timescales for when we need to get bugs/patches in and reviews for
> achieving getting our fixes in Gecko 1.9 that we're probably going to be
> doing our next release on.
If there are regressions/problems in Gecko that affect your apps, you
should set the blocking-1.9? flag on the bug and comment saying this bug
Seamonkey is affected. People take those bugs seriously, in my personal
experience working on widget/ we have spent time fixing bugs that break
Camino.
You should also try to attend the Firefox 3/Gecko 1.9 meeting, held
Tuesday, and announced in this newsgroup. At least one person from your
project should listen in and give updates to the rest of the developers,
that's where this sort of thing gets discussed. There's also the
#granparadiso channel on IRC.
In short: We don't really know when the final release is going to be.
Beta 2 is already in the rc stage, it's too late to get things in there,
and people are thinking of doing the code freeze for beta 3 around
January 22nd, that was just floated as a tentative date today. Nobody
knows how many betas, but I doubt that beta 3 will be the last one.
That said, I think us folks working on Firefox 3 / Gecko 1.9 could make
the decisions about scheduling a little more knowable, i.e. by updating
roadmap pages, even if the information is "We don't know for sure, but
here are some thoughts."
-Colin
beel...@gmail.com
representing the Firefox Project but I would consider him as Mozilla
developer, or at least as someone with enough competence to be quoted
(I still think that SeaMonkey belogns to Mozilla ;-), so I think that
it is enough for my purpuses, and when some other developers here in
the list agree with him so it's even better for me :-)
And sorry that I switched to German, I did it because for me the
discussion was finished, and I only wanted to thank Robert for his
help, next time I won't do that publicly but write a personal email.
Regards
beel
smi...@yahoo.com
wow i actually get to post in the same newsgroup as people working on
firefox 3 that is cool, you guys are like celebrities, I've been using
the minefield ever since alpha 1, i'm already using firefox beta 3,
keep up the good work guys, i can't wait for firefox 3 to be
officially released so that i can start using FIREFOX 4. alpha of
course