Re: Issue tracker usage stratagy
Posted: Tue Jun 16, 2015 8:05 am
#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
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