Releases/Firefox 3.6b1/BuildNotes: Difference between revisions

Line 145: Line 145:


====Update verify====
====Update verify====
The updater verify bumper is known to not handle the branding switch (from unofficial/Namoroka to official/Firefox). We should expect the automatically triggered runs will fail.
The update verify bumper doesn't handle the branding switch (from unofficial/Namoroka to official/Firefox).  


Landed [https://bugzilla.mozilla.org/attachment.cgi?id=405435 this patch] in the build/tools repo after updates bumps the verify configs. The FtpPoller fail means we don't have to clean up verify runs with wonky configs.
Landed [https://bugzilla.mozilla.org/attachment.cgi?id=405435 this patch] in the build/tools repo after updates bumps the verify configs. The FtpPoller fail means we don't have to clean up verify runs with wonky configs.


''Make sure to ask QA to test WinCE updates on their devices when announcing updates on betatest.''
Got the expected diffs in removed-files for partial updates on linux/mac, particularly on mac which now combines components/*.xpt like the other platforms did. We exclude removed-files from the partial mar and I think that diff is harmless. On windows the partial log will has lots of  
 
Expect to see diffs in removed-files for partial updates, particularly on mac which now combines components/*.xpt like the other platforms did. We exclude removed-files from the partial mar and I think the diff is harmless. On windows the partial log will have lots of  
  EXECUTE PATCH c
  EXECUTE PATCH c
  EXECUTE PATCH c
  EXECUTE PATCH c
  EXECUTE PATCH d
  EXECUTE PATCH d
This was fixed by {{bug|508746}} between a1 and b1, so will show up b1->next.release update verify.
This was fixed by {{bug|508746}} between a1 and b1, so will show up b1->next.release update verify.
The usual chk file differences on win32, now three of them with the addition of nssdbm3.chk.


====Update Bouncer====
====Update Bouncer====
Confirmed users
4,293

edits