Closed Bug 644635 (publish-js185src) Opened 13 years ago Closed 13 years ago

Publish JS 1.8.5 source release

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wes, Assigned: jabba)

References

()

Details

Please publish the JS 1.8.5 source release.

File:   http://www.page.ca/~wes/js-releng/js-1.8.5-final/js185-1.0.0.tar.gz
md5sum: c2a0b6732953bf519764ee488840b1c5
Target: http://ftp.mozilla.org/pub/mozilla.org/js/js185-1.0.0.tar.gz

Future note to self: To create tar ball release, use the Download tip as .gz link from BitBucket, untar, rename the top-level directory, and tar it back up again.
RelEng doesn't have write access to this directory, off to Server Ops.
Assignee: nobody → server-ops
Component: Release Engineering → Server Operations
QA Contact: release → mrz
Hey, Server Ops -- Since the opportunity presents itself, I'm going to take a couple of trivial patches this afternoon. Will ping back with a new md5sum when we're ready to roll.
New md5sum: a4574365938222adca0a6bd33329cb32

Ready to roll, please upload to ftp.mozilla.org
Done.
Assignee: server-ops → jdow
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Thanks, Justin.

What's the best way to request this for the next release when the time comes?
Honestly, I have no idea what the correct procedure is for this. I scp'd the file there manually as root, but looking at the previous releases, those files are owned by bclary. Perhaps he knows the right way to do this.
Thanks, Justin.

CCing bc in the hopes that he does. :)
Justin, that is essentially what I did. I don't know of any special procedure other than that.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.