best practices for binaries/build results?

Is there an established procedure or recommendation for storing
versioned binaries and build by-products. I don't really want them
pushed back to the source repository because they are mostly
reproducible, have a short useful life, and are too big to let them
accumulate forever. Are there any common conventions that people use to
consistently tie the results that need to go through testing and
possibly production to the tag/revision that generated them in a way
that works across different projects? Or would it be a good idea to
push them into a separate repository that could be managed differently
using some convention for tag names to tie them together?

-- 
   Les Mikesell
     lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org