2.0.0.2/1.5.0.10 security release update - new target ship date: Thursday 2/22

We had to respin for 
https://bugzilla.mozilla.org/show_bug.cgi?id=370445, and now have 
Firefox 2.0.0.2 rc4 and 1.5.0.10 rc2 builds. We also had to re-fix the 
permissions issue with DE (temporarily disabled watch for files 
effected), and will look for a more permanent fix for the next release.  
Looks like these latest rc builds might be it...

Build and QA are wrapping up work for these latest rc builds and we are 
shooting for a target ship date of Thursday 2/22 (Thunderbird will 
follow the next week).

Detailed schedules/tasks and general info can be found on the wiki 
http://wiki.mozilla.org/Firefox:1.5.0.10-2.0.0.2.  Thanks!

- Jay

Jay Patel wrote:
> We had to respin for 
> https://bugzilla.mozilla.org/show_bug.cgi?id=370445, and now have 
> Firefox 2.0.0.2 rc4 and 1.5.0.10 rc2 builds. We also had to re-fix the 
> permissions issue with DE (temporarily disabled watch for files 
> effected), and will look for a more permanent fix for the next release.  
> Looks like these latest rc builds might be it...
> 
> Build and QA are wrapping up work for these latest rc builds and we are 
> shooting for a target ship date of Thursday 2/22 (Thunderbird will 
> follow the next week).
> 
> Detailed schedules/tasks and general info can be found on the wiki 
> http://wiki.mozilla.org/Firefox:1.5.0.10-2.0.0.2.  Thanks!

Sources are missing for this round of RCs.  If it's possible to get them 
up as early in the week as possible, it would help out a bunch.  I'm out 
on vacation until March 2 and any help you can give Martin who will be 
handling this security release for Red Hat in my stead would be much 
appreciated.

In a side note, I thought the source generation and uploading was 
supposed to be automated?  I'm still willing to help with writing these 
scripts/tools as they appear to still be pretty error prone (every 
second or third or so release has these source ball missing issues).

Christopher Aillon schrieb:
> Sources are missing for this round of RCs.  If it's possible to get them 
> up as early in the week as possible, it would help out a bunch.  I'm out 
> on vacation until March 2 and any help you can give Martin who will be 
> handling this security release for Red Hat in my stead would be much 
> appreciated.

As a note, the SeaMonkey project is planning to release a SeaMonkey 
1.0.8 in parallel with FF 1.5.0.10 (candidate builds, including source 
tarballs are up already).

We're also planning to do a SeaMonkey 1.1.1 from the same Gecko as FF 
2.0.0.2, but with a bunch of mail- and suite-specific fixes taken from 
after the firefox release tag was cut. This comes from the same source, 
and we're in the process of generating and uploading candidate builds 
and source tarballs (they're done and uploaded with the Linux builds 
automatically in my setup). Depending on QA and what they find, we may 
move the cvs tag for some specific files, redo candidates, and maybe 
release this version later than Thursday. We'll see about that.

More details, as always, in the relevant thread in m.d.a.seamonkey

Robert Kaiser