Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=SCS_REPO_MAINTENANCE_R4, 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

Creates a tag at the end of the iteration. Regular task.

Task requirements

• Review the previous revision of this task SCS_REPO_MAINTENANCE_R4
• Review PLATFORM_STANDARDS_REPOSITORY
• Create a tag at the end of Iteration5.
  • Working with the repository should fulfill requrements listed in PLATFORM_STANDARDS_REPOSITORY
• Review the contents of the repository, discuss with the team leader deletion of obsolete content (see implementation idea)

Task result

A tag in the repository. Cleared repository

Implementation idea

Cleaning the repository should include deletion of files with extensions .txt~ for example. For the tag you may use the design section of previous revision of this task.

Related

SCS_REPO_MAINTENANCE_R3

How to demo

Explain what is done. Present implementation section of the task.

Design

• Discuss with the release team the results of the merging of the experimental, release and trunk
• After the merging is finished create tag for the fifth iteration as explained below:

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://sophie2.org/sophie2/trunk \
             svn://sophie2.org/sophie2/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.

• How to create a tag on Windows with ​TortoiseSVN:
  • Update first.
  • Go to "trunk" folder in your local repository
  • Right click on it
  • TortoiseSVN -> Branch/tag
  • Dialog window appears. Now instead of ​svn://sophie2.org/sophie2/trunk (or ​svn://asteasolutions.net/sophie-jr/trunk) use ​svn://sophie2.org/sophie2/tags/m??-??? (or ​svn://sophie2.org/sophie2/tags/m??-???). Here m??-??? stands for the milestone and its name for example m01-pre1.
  • It is obligatory to write a comment when you commit.
  • Tags must be created at the end of each iteration when the work is frozen.
  • You can download TortoiseSVN from ​here.

• The following files' names must be corrected.

  2009-02-23-boyan.txt
  2009-02-24-boyan.txt
  2009-02-25-boyan.txt
  2009-02-26-boyan.txt
  2009-02-27-boyan.txt
  

The proper format is id-YYYY-MM-DD.txt

• There are also some files with .txt~ and .TXT extensions, which need to be fixed.
• Revise the PLATFORM_STANDARDS_REPOSITORY and make some corrections if needed in the implementation phase (finding mistakes will be easier when following the steps for creating tag for example).

Implementation

• The release team successfully merged experimental, release and trunk branches.
• Tag m04-pre4 was created, following the steps in design.
• The PLATFORM_STANDARDS_REPOSITORY was checked
  • some old links were removed
• File names in the manage directory were corrected.

Testing

^{(Place the testing results here.)}

Comments

^{(Write comments for this or later revisions here.)}