FF/TB 1.5.0.4 code freeze/Release Candidiate builds available

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

FF/TB 1.5.0.4 code freeze/Release Candidiate builds available

Tim Riley-3
We are now under code freeze for 1.5.0.4.  Feel free to jump in and
check it out.  Builds are available here:

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/1.5.0.4-candidates/rc2/
ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/1.5.0.4-candidates/rc2/

These are undergoing Basic Functional Tests and bug fix verifications.

Next Milestones:
* Release Candidate testing window: May 12 - May 19th
* L10n builds available:  May 16th
* Final Release: May 31st

Useful links:
* Community Page/Test Plan:
     http://wiki.mozilla.org/Firefox:1.5.0.4:Community
* Schedule:
     http://wiki.mozilla.org/Firefox:1.5.0.4:Schedule
_______________________________________________
dev-quality mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-quality
Reply | Threaded
Open this post in threaded view
|

Re: FF/TB 1.5.0.4 code freeze/Release Candidiate builds available

Robert Kaiser
Tim Riley schrieb:
> We are now under code freeze for 1.5.0.4.  Feel free to jump in and
> check it out.

Just FYI, the SeaMonkey project plans to do a 1.0.2 release off Gecko
1.8.0.4 that should hopefully ship in parallel with Firefox 1.5.0.4, but
we still have to fix one security issue in SeaMonkey-specific code (xpfe
tabbrowser to be exact, for those who have the privs to see it, it's bug
335335).
We'll try to get a fix for this bug in either into the frozen tree with
driver approval or do it on our release minibranch. We're blocking our
release on that bug though and hope to have a fix soon.

Robert Kaiser
_______________________________________________
dev-quality mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-quality
Reply | Threaded
Open this post in threaded view
|

Re: FF/TB 1.5.0.4 code freeze/Release Candidiate builds available

Tim Riley-3
Robert Kaiser wrote:

> Tim Riley schrieb:
>> We are now under code freeze for 1.5.0.4.  Feel free to jump in and
>> check it out.
>
> Just FYI, the SeaMonkey project plans to do a 1.0.2 release off Gecko
> 1.8.0.4 that should hopefully ship in parallel with Firefox 1.5.0.4, but
> we still have to fix one security issue in SeaMonkey-specific code (xpfe
> tabbrowser to be exact, for those who have the privs to see it, it's bug
> 335335).
> We'll try to get a fix for this bug in either into the frozen tree with
> driver approval or do it on our release minibranch. We're blocking our
> release on that bug though and hope to have a fix soon.
>
> Robert Kaiser
Thanks for the update!  You are great at keeping us aware of the
synchronization here.  We should be able to  integrate the  SeaMonkey
fix either way.  I don't want to speak for the rest of the Release Team,
but in the past we have been fine with taking SeaMonkey-specific changes
to the frozen branch.

--Tim
_______________________________________________
dev-quality mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-quality
Reply | Threaded
Open this post in threaded view
|

Re: FF/TB 1.5.0.4 code freeze/Release Candidiate builds available

Robert Kaiser
Tim Riley schrieb:

> Robert Kaiser wrote:
>> Just FYI, the SeaMonkey project plans to do a 1.0.2 release off Gecko
>> 1.8.0.4 that should hopefully ship in parallel with Firefox 1.5.0.4,
>> but we still have to fix one security issue in SeaMonkey-specific code
>> (xpfe tabbrowser to be exact, for those who have the privs to see it,
>> it's bug 335335).
>> We'll try to get a fix for this bug in either into the frozen tree
>> with driver approval or do it on our release minibranch. We're
>> blocking our release on that bug though and hope to have a fix soon.
>>
> Thanks for the update!  You are great at keeping us aware of the
> synchronization here.  We should be able to  integrate the  SeaMonkey
> fix either way.  I don't want to speak for the rest of the Release Team,
> but in the past we have been fine with taking SeaMonkey-specific changes
> to the frozen branch.

At the moment it looks like further investiation indicates that this
security issue might not exist after all. We were warned that there
might be a potential risk with using a certain function, but it looks
like our useage of the fuction is actually safe after all. :)

Robert Kaiser
_______________________________________________
dev-quality mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-quality