868986 - tracking bug for build and release of firefox 22.0

Status: RESOLVED FIXED

(Release Engineering :: Release Requests, defect)

Comment 1

[Chris AtLee [:catlee]]

For this release (and all future final release builds until bug 865701 is fixed), we will be doing a build 2 shortly after build 1 has completed, on the same changeset.

Build 2 will start after QA signs off on the test snippets.

To hide build 2's files, we'll need to drop a .htpasswd and .htaccess file in the build2 candidates dir.

Comment 2

[[e-mail] (:bhearsum)]

(In reply to Chris AtLee [:catlee] from comment #1)
> For this release (and all future final release builds until bug 865701 is
> fixed), we will be doing a build 2 shortly after build 1 has completed, on
> the same changeset.
> 
> Build 2 will start after QA signs off on the test snippets.
> 
> To hide build 2's files, we'll need to drop a .htpasswd and .htaccess file
> in the build2 candidates dir.

This is all documented here now: https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Do_another_build_of_the_release

Comment 3

[[e-mail] (:bhearsum)]

Oops, didn't mean to close this.

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

Re the documentation, please note that if RelMan decide build 1 will be shipped instead of 2 then we need to do some extra work before using the automation again, eg  https://wiki.mozilla.org/Releases/Firefox_21.0/BuildNotes#Reset_automation_to_build3

Similarly build 3 instead of 4, build N instead of N+1.