Release Process

We need to think about how we do releases. concurrent-programming-web!4 (merged) is currently linking directly to master's latest artifact, which will expire after 4 weeks by default. I'm not sure what the best answer to this is, but it might be setting up a dedicated release branch (or using master) and adding a deploy job that creates a permanent, likely versioned download somewhere on pseuCo.com, probably a subdomain. The compiler should likely get the same treatment. What do you think?