Closed Bug 540000 Opened 15 years ago Closed 14 years ago

Tracking bug for build and release of Firefox 3.6rc2

Categories

(Release Engineering :: General, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: catlee, Unassigned)

References

()

Details

Attachments

(3 files)

      No description provided.
Attachment #421878 - Flags: review?(ccooper)
No need for version bump
Comment on attachment 421878 [details] [diff] [review]
release automation bump

Looks good.
Attachment #421878 - Flags: review?(ccooper) → review+
Comment on attachment 421878 [details] [diff] [review]
release automation bump

changeset:   1952:51d8e68311d6

checked in with changeset 448d0d2d310c
Attachment #421878 - Flags: checked-in+
See bug 535567 comment #9 and 11 for changes needed for updates.
... so that people who downloaded 3.6rc1 from the website get updated to 3.6rc2. I'm guessing that we'll want to update users on beta and release simultaneously, so we probably don't need to seperate out those snippets with useBetaChannel until 3.6.1. Not hard to do with some shell in any case.

This should land before we complete signing.
Attachment #421947 - Flags: review?(catlee)
Attachment #421947 - Flags: review?(catlee) → review+
Comment on attachment 421947 [details] [diff] [review]
Generate snippets for release channel too

cvs commit: Examining .
Checking in moz192-branch-patcher2-wince.cfg;
/cvsroot/mozilla/tools/patcher-configs/moz192-branch-patcher2-wince.cfg,v  <--  moz192-branch-patcher2-wince.cfg
new revision: 1.2; previous revision: 1.1
done
Checking in moz192-branch-patcher2.cfg;
/cvsroot/mozilla/tools/patcher-configs/moz192-branch-patcher2.cfg,v  <--  moz192-branch-patcher2.cfg
new revision: 1.18; previous revision: 1.17
done
Attachment #421947 - Flags: checked-in+
Attachment #422123 - Flags: review?(catlee)
Attachment #422123 - Flags: review?(catlee) → review+
Comment on attachment 422123 [details] [diff] [review]
WinCE patcher config

Checking in moz192-branch-patcher2-wince.cfg;
/cvsroot/mozilla/tools/patcher-configs/moz192-branch-patcher2-wince.cfg,v  <--  moz192-branch-patcher2-wince.cfg
new revision: 1.3; previous revision: 1.2
done
Attachment #422123 - Flags: checked-in+
Back in the pool waiting for QA signoff on wince stuff.
Assignee: catlee → nobody
I asked "what to do with the pending FF3.6.0 WinCE builds?" in today's Firefox release meeting. 

All other OS shipped. Testing WinCE is dead last on the QA priority list. However, we'll leave this bug open for a little longer to track, in case we do get the "go" and need to work through a quick guess of remaining steps: 
* renaming files, *SUMS refreshing and signing, bouncer, push, enable snippets



Full build notes are here: https://wiki.mozilla.org/Releases/Firefox_3.6/BuildNotes
Whiteboard: holding open for wince
moving to future
Component: Release Engineering → Release Engineering: Future
joduinn shouldn't we close this? I don't that holding open for WinCE still valid at this point.
Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
We've shipped 3.6rc2 and 3.6 final. If we want to ship WinCE for those at some point in the future then we can open a new bug.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: holding open for wince
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: