Bug 635486 is going to collect all the release logs to a single location for the first time, and creates an opportunity to archive those for future reference. A builder which is run at the very end of the release (and possibly also handles the latest symlinks) would be one way to do this.

Mass move of bugs to Release Automation component.

For now, we're keeping them in stage:~cltbld/old-candidates-dirs/firefox/stripped/

Will s3 do this for us?

FWIW, we're archiving to http://stage.mozilla.org/pub/mozilla.org/firefox/candidates/archived/ these days, via ~ffxbld/archive_candidate_dir.sh. We'll need to reimplement cleanup of candidates builds, which gives an opportunity to do whatever we want with logs.