Issue tracker usage stratagy

User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

Re: Issue tracker usage stratagy

Post by Josef Templ »

#19 is "Adding 16-bit Unicode support for Component Pascal identifiers".

Every change in the repository that is related with this issue should
reference #19. This way we get what is called "bidirectional traceability"
or "two way traceability". The two directions are:
1. From an issue (in redmine) you can go to all related changes (in git).
2. From a change (in git) you can go to the issue (in redmine).
The connection between the issue and the change(s) is the issue number referenced in a commit.

It is a well established software engineering concept used all over the world.
I have tried to explain this multiple times and there were no objections so far.

You can call this a bug classifier, if you like, but this is not an established term.

- Josef
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: Issue tracker usage stratagy

Post by Ivan Denisov »

Josef, you system of issues classification passed all the examinations :)

Now we can say, that it can be our Center Standard.

For new release we shall make new numbers. But again group all the commits similar way.
Post Reply