Please add developer's guideline for contribution #848
Description
No guideline for making changes/bug fixing
We need to establish some process each developer should follow to assure code quality, functional correctness and design consistency of the changes.
Let's define:
- developer steps to configure Jagger development environment
- how to test changes (CI?)
- who we can reach for code review/pull request approval
- how to release changes
- notification in GD mail about new version with release notes would be usefull
- how to update documentation
- ...