All the FE/CRU static content is under /static/RND/

However, if an external resource wants to reference a (say) changeset icon, then they have to tie their url to a specific build of FE/CRU.

We should 302 tmp redirect /static/current/XYZ to /static/RND/XYZ as a service to external consumers.

We should NOT use /static/current/ internally as that would mean all our image loads require two http requests.

We also need a place to advertise/document this service. Perhaps create (or raise a subtask) "Web Resources" section to the development hubs that clear indicates this is available. That page should also outline the general url structure of FE/CRU

/api/ the original api
/browse/repname/~CONSTRAINT/path etc
/search/?whatever&csv
/cru/REVIEW_KEY
/plugins/servlet etc
/whatver-the-rest-apis are