Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
devel:documentation:modules_extras [2019/12/17 07:59] fiserp [CzechIdM - extras] |
devel:documentation:modules_extras [2020/02/18 10:04] sourek |
||
---|---|---|---|
Line 5: | Line 5: | ||
===== Developing and releasing ===== | ===== Developing and releasing ===== | ||
- | <note important> | + | How to develop a new feature in extras: |
+ | |||
+ | - Create a specification page in private section | ||
+ | - Usecases - why we or user need this feature, what problem does it solve? | ||
+ | - Why is it in extras and not in core, or other module? | ||
+ | - Functional specification - how should it work, edge cases | ||
+ | - Ask a module owner, if this feature can be a part of extras and in which version it will be published | ||
+ | - Create ticket | ||
+ | - Implement | ||
+ | - Create merge request to develop | ||
+ | - Get someone from product team, or module | ||
+ | - After successfull review, ask module owner to merge you code | ||
+ | |||
+ | Rules for code review: | ||
+ | * All new features have at least 80 percent test coverage | ||
+ | * All features are documented | ||
+ | * There are no sonar issues in commited code | ||
+ | * Changelog is updated | ||
+ | * Feature is by default turned off (can be enabled either by processor, or configuration property) | ||
+ | |||
+ | |||
+ | <note important> | ||
* When developing, use our standard gitflow: | * When developing, use our standard gitflow: |