1.5a schedule
Asa Dotzler
<http://www.mozilla.org/roadmap.html#milestone-schedule> has been
adjusted with two weeks added to the Mozilla 1.5a milestone period. The
new 1.5a freeze date is July 9.
--Asa
Asa Dotzler
This schedule adjustment is because we're still working on 1.4 (though
we're very close now).
--Asa
Rainer Kugland
Does anybody know the schedules for 1.5? Will it be delayed for months
now since there are no netscape developers left?
RK
Benedikt Kantus
> Does anybody know the schedules for 1.5? Will it be delayed for months
> now since there are no netscape developers left?
Well, this doesn't mean that those who have been laid off won't work on
Mozilla anymore. But of course everybody should understand that some or
most of them have other things in mind at the moment.
For what I know, there is no date set for the 1.5 release. It will be
released "when it is ready", as Gerv mentioned some weeks earlier. And
at the moment, it's definitely not ready, because 1.5a has been released
as a Seamonkey suite.
The fact that AOLTW laid off several hackers will slow things down too.
HTH.
-Bene
--
There are only 10 types of people in the world:
Those who understand binary and those who don't.
Boris Zbarsky
> For what I know, there is no date set for the 1.5 release. It will be
> released "when it is ready", as Gerv mentioned some weeks earlier.
That doesn't seem, to me, to be the way we've released previous
milestones. They're always just dated snapshots of the trunk, with
enough patching up done so that they are not unbearable to use. There
is nothing in the way of goals for the milestone to judge when it's
ready other than general "people will actually download this because
it's not unusable" feeling.
> And at the moment, it's definitely not ready, because 1.5a has been released
> as a Seamonkey suite.
If the transition away from the suite is to happen, it had better happen
in some sort of alpha milestone. This is not the sort of change you do
in the last week of a cycle.
-Boris
Michael Lefevre
>
>> Does anybody know the schedules for 1.5? Will it be delayed for months
>> now since there are no netscape developers left?
>
> Well, this doesn't mean that those who have been laid off won't work on
> Mozilla anymore. But of course everybody should understand that some or
> most of them have other things in mind at the moment.
indeed.
> For what I know, there is no date set for the 1.5 release. It will be
> released "when it is ready", as Gerv mentioned some weeks earlier. And
> at the moment, it's definitely not ready, because 1.5a has been released
> as a Seamonkey suite.
Some comments to that effect were made. But, from the decision
(recorded in the mozilla meeting minutes and in the roadmap) to add just a
couple of weeks to the schedule for 1.5, and try and stick to it, it looks
like a decision hasn't been made to switch to a "bug-driven" timetable.
Therefore, 1.5 will be released roughly on schedule, incorporating
whatever work has been done at that time (which obviously won't include a
switch to Firebird). A most recent change to roadmaps was to indicate
that Firebird 0.7 should coincide with Mozilla 1.5.
--
Michael
Gervase Markham
>> For what I know, there is no date set for the 1.5 release. It will be
>> released "when it is ready", as Gerv mentioned some weeks earlier.
>
> That doesn't seem, to me, to be the way we've released previous
> milestones. They're always just dated snapshots of the trunk, with
> enough patching up done so that they are not unbearable to use.
bz is right - I'm not sure where I said that, but I might have just been
being flippant. The 1.5 alpha branch will be released soon, and the
current plan is to stick to the schedule outlined in the roadmap. What
that means for the Seamonkey/Mozilla Firebird transition is probably not
yet completely clear.
Gerv
Benedikt Kantus
Ok that might have been a mistake on my side. I just implied that the
transition would have been finished by the time 1.5 will be released.
What you actually said was that the *transition* will happen when the
birds are ready, not the 1.5 release. Sorry.
Jay Garcia
On 18.07.03 03:34, Gervase Markham wrote:
--- Original Message ---
Pardon me, but I've seen the answer(s) dozens of times but still confused.
Why does my Mozilla UA say 1.5b if we'er in 1.5 Alpha ?? <ducking>
Thanks
--
Jay Garcia - Always A Netscape Champion
The UFAQ Lives - http://www.UFAQ.org http://www.UFAQ.org/text_version.html
Post To Group Only - No Email Please
Giacomo Magnini
> Why does my Mozilla UA say 1.5b if we'er in 1.5 Alpha ?? <ducking>
Because you installed a mozilla nightly (which is based on 1.5b) while
1.5a is on its own "branch" and will be released shortly (after a few
fixes are in). 1.5b has already taken lots of new checkins and is the
current development version. 1.5a is in bugfix mode and to be released RSN.
Cheers, Giacomo.
Boris Zbarsky
> Boris Zbarsky wrote:
>
>>> For what I know, there is no date set for the 1.5 release. It will be
>>> released "when it is ready", as Gerv mentioned some weeks earlier.
>>
>>
>> That doesn't seem, to me, to be the way we've released previous
>> milestones. They're always just dated snapshots of the trunk, with
>> enough patching up done so that they are not unbearable to use.
>
>
> bz is right - I'm not sure where I said that, but I might have just been
> being flippant.
Just to clarify, the milestones _are_ released "when they are ready",
but the condition of being ready is achieved when it is usable by
people, such that they are able to download it and use it and provide
feedback. So Gerv is perfectly right that 1.5a, 1.5, etc will be
released "when it is ready", but the original poster I was replying to
was mis-interpreting what "ready" meant in that context....
-Boris
Rainer Kugland
> Just to clarify, the milestones _are_ released "when they are ready",
> but the condition of being ready is achieved when it is usable by
> people, such that they are able to download it and use it and provide
> feedback. So Gerv is perfectly right that 1.5a, 1.5, etc will be
> released "when it is ready", but the original poster I was replying to
> was mis-interpreting what "ready" meant in that context....
take place? I don't ask for a fixed date but at least for the season of
the year...
Thanks
RK