436853 - update staging 1.9 release automation to build 3.0.1

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[[e-mail] (:bhearsum)]

Attachment: [checked in] update staging 1.9 bootstrap config.

Comment 1

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

Comment on attachment 323355 [details] [diff] [review]
[checked in] update staging 1.9 bootstrap config.

r+. Both appVersion and oldAppVersion are optional and won't be needed for 3.0.x, so could be removed on checkin.

Looking at this reminds me that Tag::Bump is going to expect a version of 3.0.1pre and a milestone of 1.9.0.1pre in the CVS mirror. So you'll need a version bump checked into /builds/cvsmirror.clean on the staging master (no review req'd).

Comment 2

[[e-mail] (:bhearsum)]

Comment on attachment 323355 [details] [diff] [review]
[checked in] update staging 1.9 bootstrap config.

Checking in configs/fx-moz19-staging-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz19-staging-bootstrap.cfg,v  <--  fx-moz19-staging-bootstrap.cfg
new revision: 1.31; previous revision: 1.30
done

Comment 3

[[e-mail] (:bhearsum)]

This seems to be going fine now. I had to manually update the patcher config (on the cvsmirror) to make it look like 3.0 was released. I also had to manually rename some files and create a FIREFOX_3_0_RELEASE tag to make update_verify work. Other than that, it's been a clean run. Just finishing stage/update_verify right now.

Comment 4

[[e-mail] (:bhearsum)]

Had some spurious win32/mac update_verify failures. Nothing out of the ordinary though, AFAIK.