wiki:SCS_REPO_MAINTENANCE_R2
Last modified 12 years ago Last modified on 12/19/08 14:50:52

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=SCS_REPO_MAINTENANCE_R2, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

In this revision should be created a tag. Make sure all of the team members do have accounts for the new repository.

Task requirements

  • Create a tag at the beginning of week 4 of this sprint
  • This tag should be created in the new repository
  • Review the branch created for the release.
  • Use platform standards repository to create the tag and test if the instructions are detailed enough. Add feedback to the PLATFORM_STANDARDS_REPOSITORY
  • See the mail list and make sure all of the team members do have accounts for the new repository.

Task result

A tag. Comment in PLATFORM_STANDARDS_REPOSITORY.

Implementation idea

See how the tag is created in previous revision. Use the new repository address.

SCS_REPO_MAINTENANCE_R0
SCS_REPO_MAINTENANCE_R1

How to demo

Explain is the tag created. Does each team member have account for the new repository. Feedback of PLATFORM_STANDARDS_REPOSITORY.

Design

  • Read the section about creating a tag using TortoiseSVN or creating a tag on Linux

Creating Tag

Another common version control concept is a tag. A tag is just a “snapshot” of a project in time. In Subversion, this idea already seems to be everywhere. Each repository revision is exactly that—a snapshot of the filesystem after each commit.

However, people often want to give more human-friendly names to tags, like release-1.0. And they want to make snapshots of smaller subdirectories of the filesystem. After all, it's not so easy to remember that release-1.0 of a piece of software is a particular subdirectory of revision 4822.

  • How to create a tag on Linux
    $ svn copy svn://asteasolutions.net/sophie2-repo/trunk \
               svn://asteasolutions.net/sophie-jr/tags/m??-??? \
          -m "Comment."
    Committed revision 351.
    

Here m??-??? stands for the milestone and its name for example m01-pre1.
After the copy completes, the new m??-??? directory is forever a snapshot of how the project looked in the HEAD revision at the time you made the copy. Of course you might want to be more precise about exactly which revision you copy, in case somebody else may have committed changes to the project when you weren't looking. So if you know that revision 350 of /sophie2-repo/trunk is exactly the snapshot you want, you can specify it by passing -r 350 to the svn copy command. In Subversion, there's no difference between a tag and a branch. Both are just ordinary directories that are created by copying. Just as with branches, the only reason a copied directory is a “tag” is because humans have decided to treat it that way: as long as nobody ever commits to the directory, it forever remains a snapshot. If people start committing to it, it becomes a branch.

Implementation

  • All team members have accounts for the new repository.
  • Created new tag for the last iteration, called m02b-pre02b
  • The tag is stored in svn://sophie2.org/sophie2/tags/m02b-pre02b
  • Checked the instructions for creating a tag (everything is ok)

Testing

Comments