Skip to Main Content
Pragmatic Guide to Subversion
book

Pragmatic Guide to Subversion

by Mike Mason
November 2010
Intermediate to advanced content levelIntermediate to advanced
150 pages
2h 55m
English
Pragmatic Bookshelf
Content preview from Pragmatic Guide to Subversion
28Tagging a Release

When creating a build of your software, especially one that will be released to a customer, it’s important to know exactly what source code was used. We can use a Subversion tag to record which revisions of files were used in a build.

As part of the release process, someone needs to compile the software. Usually this is a manual process done by one of the developers, but it can also be automated. You might have a build box that automatically builds your software every time a developer makes a change. Either way, you should have a process for building the software and assigning it a build number.

Use the Subversion copy command to copy your working copy to a new directory in your project’s tags directory. You should create ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Reinventing the Organization for GenAI and LLMs

Reinventing the Organization for GenAI and LLMs

Ethan Mollick

Publisher Resources

ISBN: 9781680500035Errata Page