Closed Bug 468468 Opened 16 years ago Closed 16 years ago

Sign Thunderbird 3 Beta 1 Build 2 bits

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gozer, Assigned: nthomas)

References

()

Details

Files are ready to be signed, and have been massaged into the new directory layout. http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/3.0b1-candidates/build2-newlayout/
I'll start this shortly.
Assignee: nobody → bhearsum
Priority: -- → P2
While signing was running I noticed that the win32 complete MARs are busted. Filed bug 468488 on that - I'm going to hold off pushing back signed builds until I know if you want to respin win32 l10n for this.
Handing off to Nick. Gozer, if you decide to live with the broken MARs he'll push the signed builds back to stage. Nick, they should go into 3.0b1-candidates/build2-newlayout.
Assignee: bhearsum → nthomas
Well, since the complete .MARs are only needed once we release 3.0b2, couldn't you just get the existing signed bits back to stage first? Then I can regenerate the correct .MARs and get them signed sometime later. I am asking because the plan currently is to release tomorrow, so, producing the corrected .MARs _before_ release time might be tricky. Is there any problem with that solution? I can just *not* include any .MARs for the time being without adverse effect, right ?
(In reply to comment #4) > Is there any problem with that solution? I can just *not* include any .MARs for > the time being without adverse effect, right ? If you're not updating alpha builds to b1 then you can figure this out later. I'll upload them.
Uploaded now. Had some issues with permissions due to files/dirs in build2-newlayout being owned by tbirdbld, while I was pushing with cltbld. Sorted out and 'find -mtime -1' looks fine, but do remove the g+w I did if you don't want that. Don't forget to remove your hidden files (eg .foo) and unsigned/ too.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.