Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=UNPLANNED_REPO_MAINTENACE_R1b, compact) failed

current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

For this revision of the task, you must create new tag, and make sure that everyone commits according the rules.

Task requirements

• Create new tag for the previous iteration
• Decide which is the best place to put the commit rules and append them there - a candidate for this is REPO_MAINTENANCE
• Check the commits from last iteration to make sure that everybody commits according to the rules
• If someone doesn't follow them, you must make him to do so
• See SCS_REPO_MAINTENANCE_R1, create a wiki page from it's Implementation Idea (see if sophie-jr and sophie2 are the same and use sophie2.)
• Expand the document with linux instructions on branching/tagging.

Task result

The result of this task must be new tag for last iteration and no commits without proper comment.

Implementation idea

• Create tag named m02-pre2
• Check the comments using tortoise svn
• Create a wiki page REPO_MAINTENANCE and meet the mentioned requirements.

Related

SCS_REPO_MAINTENANCE_R0
SCS_REPO_MAINTENANCE_R1
SCS_REPO_MIGRATE_R0
SCS_REPO_MIGRATE_R1

How to demo

Show the new tag. Show the commit rules and where they are stored. Show the instructions in REPO_MAINTENANCE

Design

REPO_MAINTENANCE will look this way: Creating tag:

• 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://asteasolutions.net/sophie2-repo/trunk (or ​svn://10.10.117.11/sophie-jr/trunk) use ​svn://asteasolutions.net/sophie2-repo/tags/m??-??? (or ​svn://10.10.117.11/sophie-jr/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.
• How to create a tag on Linux

Committing rules:

• Always write a comment which task(s) affects your commit (in other words which task you are working on).
• When you commit code be sure that it is written following the code standards.
• Committing without a comment is absolutely impermissible (that is valid even when committing only a daily report).

Implementation

^{(Implementation results should be described and linked here (from the wiki or the repository))}

Testing

Comments

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