What is the correct way to use and mark code for deployment in SVN?

Submitted by mberger@mit.edu on Thu, 01/22/2009 - 10:40

We use SVN for source control. I have the following questions:
1. When should we tag a release?
2. When should we branch a release?
3. Are there MIT-specific naming conventions that we should use with our releases?

‹ openssl question

What AMIT Does

Submitted by sml@mit.edu on Thu, 01/22/2009 - 12:26.

My team supports development teams who use SVN. We are essentially the release-managers and platform coordinators for our group. To be able to see into a project that we do not know intimately and have a self-documenting source tree if we have to rebuild a system, we inflict only a few simple rules on the development teams.

TAG every release to a test or QA system as release-[version]-[yyyymmdd] where "version" is whatever the local team does to version their software.

BRANCH every release to production as prod-[version]-[yyyymmdd].

Whatever else they do within the source tree is the team's business. This way, the rest of your department can find important builds quickly.