481469 - do a 3.1b3 -> 3.5b4 test run with release automation

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[[e-mail] (:bhearsum)]

According to the Firefox delivery meeting today we'll be going from 3.1b3 -> 3.5b4. In theory this should be totally fine, but we need to do a full end to end test run to make sure the automation and associated tools (patcher, update verify, et. al) will handle this properly.

Comment 1

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

On hold, pending confirmation of a bump to 3.5

Comment 2

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

Doing a run now, with manually set up users/stage-ffxbld/mozilla-1.9.1 to get version bump and abbreviated shipped locales (also adjusted repo setup factory to skip delete/clone on mozilla-1.9.1). No problems through tagging, including version bump.

Comment 3

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

Boo, blew up due to insufficient clean up on slaves before starting. Will try again later.

Comment 4

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

Should also check that signing changes in bug 409479 work out OK.

Comment 5

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

The only problem I hit with a mock release run was fixed by bug 486076, which just needs landing on mozilla-1.9.1. The signing test I did wasn't that rigorous because of difficulties getting staging and production machines to talk to each other, but there were no major gotchas.

Comment 6

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

Forgot to mention bug 486444, which leaves win32_info.txt with some stray characters.