Record version numbers of tested dbs

Registered by Federico Razzoli on 2013-02-18

Recording version numbers of tested DBs make it possible to mantain different versions of a software, and identifying regression bugs.

Version numbers can consist of:
* branch (that could be major.minor version number)
* revision (that could match to bzr revision or last number in release numbers)

In order to inform STK/Unit about the current version number, tested DBs can implement 3 optional functions:
* MEDIUMINT UNSIGNED get_branch_id()
* MEDIUMINT UNSIGNED get_revision_id()
Those functions provide numbers and is suitable for STK/Unit, that will use them to order/compare versions.

If those functions are there, 2 optional tables may be used to provide metainfo about branches and revisions:

branch_status:
* id
* name

branch:
* id
* name
* status_id

revision:
* id
* branch_id

PURPOSE
=======

The most obvious feature will be the ability to see the test results for:
* a given revision
* latest revisions for a given branch
* latest revisions for branches having a given status (ie: branches being still mantained)
* latest revisions for all existing branches

Some views will make these queries easier.

A less obvious feature will be the ability to identify possible regression bugs (failures or exceptions which were in x.x, then were fixed, but then came up again on x.y).

Blueprint information

Status:
Not started
Approver:
None
Priority:
Low
Drafter:
None
Direction:
Approved
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.