SCS_REPO_MAINTENANCE_R1

[Astea]

wiki page: SCS_REPO_MAINTENANCE_R1 - effort: 0.5d

Error: Macro BackLinksMenu(None) failed

operator does not exist: text = integer
LINE 1: ...,author,text,comment,readonly FROM wiki WHERE name=1391 ORDE...
                                                             ^
HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.

Analysis

Overview

The goal of this task is to make branch or tag from the previous version of our repository and to define some commit rules. This maintenance is performed regularly.

Task requirements

• decide which to use - branch or tag
• write in Implementation section how to create a branch/tag from the previous revision of the repository and create it
• define rules for the comments of the commits

Task result

• a branch/tag from the repo
• description how to do a branch/tag
• commit rules in the implementation section

Implementation idea

• one rule is to write the id and the name of the task related to your commit at the end of the comment.
• ​http://svn.collab.net/subclipse/help/index.jsp?topic=/org.tigris.subversion.subclipse.doc/html/reference/branch-tag.html

Related

SCS_REPO_MAINTENANCE_R0
PLATFORM_STANDARDS_REPOSITORY

How to demo

• Show the new tag/branch and the how-to for making it.
• Show the new commit rules.

Design

Definitions:

• A tag is just a "snapshot" of a project in time. In Subversion each revision is a snapshot of the repository file-system after each commit, and it can be used as a tag. But people often want to give some human-friendly names to tags, like release-1.0. Tag is a named snapshot, a symbolical connection with the specified revision of a project.
• Branches are created mainly for the following purposes: independent development of the current revision with the correction support in the release version, long-term independent work, using of source codes of other developers.

We will use tags, branches are not needed for now.

Tutorial for creating branch/tag with tortoise SVN:

Select the folder in your working copy which you want to copy to a branch or tag, then select the command TortoiseSVN → Branch/Tag....

The default destination URL for the new tag will be the source URL on which your working copy is based. You will need to edit that URL to the new path for your tag. So instead of ​svn://asteasolutions.net/sophie2-repo/trunk you can now use ​svn://asteasolutions.net/sophie2-repo/tags/m01-pre1

Implementation

Tag for the m01-pre1 was created.

How to create a tag 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.

There are some rules that all must follow when committing:

• 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).

Testing

Comments

Log

Error: Macro Include(wiki:SCS_REPO_MAINTENANCE_R1_LOG) failed

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

Edit
Edit Log

[pap]

by Pav

[deyan]

4p