Actions
Feature #10126
closedRearrange requirement specifications
Status:
Closed
Priority:
Urgent
Assignee:
Category:
Preset jobs, marks and tags
Target version:
Start date:
02/20/2020
Due date:
% Done:
0%
Estimated time:
Published in build:
Description
Currently requirement specifications are identified and laid out incorrectly since some of them are related with headers while other ones - with implementations in corresponding C source files. There are + and - of both approaches, but let's at least do this uniformly. We decided to relate all specifications to implementations.
Updated by Evgeny Novikov almost 5 years ago
- Status changed from New to Resolved
The feature is implemented in branch move-req-specs that is under testing right now.
Updated by Evgeny Novikov almost 5 years ago
- Status changed from Resolved to Closed
After some small fixes tests passed, so, I merged the branch to master in d752ebf5e. Do not forget to regenerate a build base for testing requirement specifications if you are using it, since I have changed names of some test cases.
Actions