Ticket #1391 (closed planned_task: obsolete)

Opened 17 years ago

Last modified 15 years ago

SCS_REPO_MAINTENANCE_R1

Reported by: Astea Owned by: todor
Priority: 3 Milestone: M02_PRE2
Component: PROJECT_COMMUNITY Version: 2.0
Keywords: Cc:
Category: unknown Effort: 0.5
Importance: 90 Ticket_group:
Estimated Number of Hours: Add Hours to Ticket:
Billable?: Total Hours:
Analysis_owners: pav Design_owners: pav
Imp._owners: todor Test_owners:
Analysis_reviewers: pap Changelog:
Design_reviewers: deyan Imp._reviewers: tanya
Test_reviewers: Analysis_score: 3.5
Design_score: 4 Imp._score: 3.5
Test_score: 0

Description (last modified by deyan) (diff)

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

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:

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

Change History

comment:1 Changed 16 years ago by todor

  • Owner changed from Astea to todor
  • Status changed from new to analyzing

comment:2 Changed 16 years ago by todor

  • Status changed from analyzing to analyzed

comment:3 Changed 16 years ago by todor

  • Status changed from analyzed to analysis_accepted

comment:4 Changed 16 years ago by pap

  • Owner changed from todor to pap
  • Status changed from analysis_accepted to designing

by Pav

comment:5 Changed 16 years ago by pap

  • Status changed from designing to designed

comment:6 Changed 16 years ago by pap

  • Owner changed from pap to pav

comment:7 Changed 16 years ago by deyan

  • Status changed from designed to design_accepted

4p

comment:8 Changed 16 years ago by deyan

  • Owner changed from pav to deyan
  • Description modified (diff)

comment:9 Changed 16 years ago by todor

  • Owner changed from deyan to todor
  • Status changed from design_accepted to implementing

took for implementation

comment:10 Changed 16 years ago by todor

  • Status changed from implementing to closed
  • Resolution set to fixed

ready in approximately 90m

comment:11 Changed 16 years ago by todor

  • Status changed from closed to new
  • Resolution fixed deleted

comment:12 Changed 16 years ago by todor

  • Status changed from new to analyzing

comment:13 Changed 16 years ago by todor

  • Status changed from analyzing to analyzed

comment:14 Changed 16 years ago by todor

  • Status changed from analyzed to analysis_accepted

comment:15 Changed 16 years ago by todor

  • Status changed from analysis_accepted to designing

comment:16 Changed 16 years ago by todor

  • Status changed from designing to designed

comment:17 Changed 16 years ago by todor

  • Status changed from designed to design_accepted

comment:18 Changed 16 years ago by todor

  • Status changed from design_accepted to implementing

comment:19 Changed 16 years ago by todor

  • Status changed from implementing to implemented

accidentally marked as resolved as fixed

comment:20 Changed 16 years ago by pavlina

  • Status changed from implemented to design_accepted

2 by Pav. There must be at least one more tag(may be one for the middle of the iteration and one for the end of the iteration).

comment:21 Changed 16 years ago by todor

  • Status changed from design_accepted to implementing

the tag will be created at the end of the current iteration, the rest is already done

comment:22 Changed 16 years ago by todor

  • Status changed from implementing to implemented

will create tag when the sprint is finished

comment:23 Changed 16 years ago by Tanya

  • Status changed from implemented to implementation_accepted

3.5

comment:24 Changed 16 years ago by deyan

  • Status changed from implementation_accepted to s3c_implementation_ok

repairing from invalid state

comment:25 Changed 16 years ago by deyan

  • Design_score set to 4
  • Design_reviewers set to deyan
  • Imp._score set to 0
  • Test_score set to 0
  • Analysis_score set to 0

added de-reviewers

comment:26 Changed 16 years ago by Tanya

  • Imp._score changed from 0 to 3.5
  • Imp._reviewers set to Tanya

comment:27 Changed 16 years ago by pap

  • Analysis_reviewers set to pap
  • Analysis_score changed from 0 to 3.5

comment:28 Changed 16 years ago by Tanya

  • Imp._reviewers changed from Tanya to tanya

comment:29 Changed 16 years ago by todor

  • Imp._owners set to todor

comment:30 Changed 16 years ago by pap

  • Category set to unknown
  • Design_owners set to pav
  • Analysis_owners set to pav

setting custom fileds

comment:31 Changed 15 years ago by deyan

  • Status changed from s3c_implementation_ok to closed
  • Resolution set to obsolete

Batch update from file query-obsoleted.csv

Note: See TracTickets for help on using tickets.