Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please add developer's guideline for contribution #848

Open
tanoshko opened this issue Dec 22, 2017 · 0 comments
Open

Please add developer's guideline for contribution #848

tanoshko opened this issue Dec 22, 2017 · 0 comments

Comments

@tanoshko
Copy link

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
  • ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant