468186 - Sign Funnelcake builds (12/15/08 ship date)

Status: VERIFIED FIXED

(Release Engineering :: General, defect, P1)

Description

[ken kovash]

Please sign funnelcake builds.  Once Kev repacks, the builds should be made ready for signing at people.mozilla.org:/tmp/funnelcake4-304-signed.tar.

Once signed, builds can be available at https://people.mozilla.org/files/partners/mozilla04/3.0.4/.

Comment 1

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

FWIW, joduinn or bhearsum could also do this.

Comment 2

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Date changed - to avoid colliding with the FF3.0.5 release. This funnelcake release would be pushed live on midnight PST between Sunday (13th) and Monday (14th), and then turned off at midnight PST between Monday (14th) and Tuesday (15th).

Nick: Kev meant to create this bug into our triage queue, not assuming you'd be doing it. Yes, any of Ben, myself, or yourself could do the signing for this release.

Comment 3

[Kev Needham [:kev]]

Packed, ready. Can we get these signed ASAP, please?
 
Available on people at:

people.mozilla.com:/tmp/mozilla04-304-unsigned.tar

md5sum is 3800742b71bf4fb6e124c9d3718dede7

Comment 4

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

Now signed at
  people.mozilla.org:/tmp/mozilla04-304-signed.tar
md5sum for the file is a2a526b8440688a3880cde26fd337a5f

I noticed that linux-i686/en-US/firefox-3.0.4.tar.bz2 was really a .tar, so I fixed that up (mv ...tar.bz2 ...tar; bzip2 ...tar).

Back to Kev to update https://people.mozilla.org/files/partners/mozilla04/3.0.4/
I can't find a "Setup download download servers for Funnelcake" bug against IT for the next step. :-S

Comment 5

[Kev Needham [:kev]]

Thanks, Nick. Good catch on the tar vs tar.bz2. 

Files are available at:

https://people.mozilla.org/files/partners/mozilla04/3.0.4/

Tarball is available on people at:

people.mozilla.com:/tmp/mozilla04-304-signed.tar]

md5 is a2a526b8440688a3880cde26fd337a5f

Comment 6

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(In reply to comment #5)
> Thanks, Nick. 

Amen to that, thanks Nick.