summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrey Oleynik (GitHub) <aoleynik@luxoft.com>2017-09-26 18:21:33 +0300
committerAndrey Oleynik (GitHub) <aoleynik@luxoft.com>2017-09-26 18:25:48 +0300
commitcf77cfe2e71837cd00467a0a6c449dce8d2bb840 (patch)
tree31fe7642a047ded5a4b767988cbcce648a6852e7
parentda4b5766ca3f1fca4caa4b4815073f72dfe37182 (diff)
downloadsdl_core-cf77cfe2e71837cd00467a0a6c449dce8d2bb840.tar.gz
Updates outdated rules and environment details
-rw-r--r--COMMITTERS.md6
-rw-r--r--CONTRIBUTING.md6
2 files changed, 8 insertions, 4 deletions
diff --git a/COMMITTERS.md b/COMMITTERS.md
index 210fceb421..dc1665ffbb 100644
--- a/COMMITTERS.md
+++ b/COMMITTERS.md
@@ -59,9 +59,7 @@ Branch name should be:
##Pull request message
* Describe the reason why you created pull request and what changes there are.
-* Add related Jira ticket as link.
- ( EXAMPLE:
- `Related: [APPLINK-xxxxx](put direct link here)`)
+* Add related GitHub issue id as link.
* If there was an old pull request, add link. ( EXAMPLE: `Old pull request is [here](put direct link here)`)
##Adding reviewers:
@@ -87,7 +85,7 @@ Branch name should be:
* Successfully passed review.
* Rebase in case of existing conflicts.
* Contributor can squash commits in case of adding same code in different commits.
-* Contact @AGaliuzov or @anosach-luxoft to merge pull request.
+* Contact [Livio team](https://livio.io/#our-team) and request to merge pull request
##Additional sources
* [Google cppint.py](https://raw.githubusercontent.com/google/styleguide/gh-pages/cpplint/cpplint.py)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 42cf5d0898..a23bcb67a2 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -2,6 +2,12 @@
Third party contributions are essential for making SDL great. However, we do have a few guidelines we need contributors to follow.
+## Environment
+Currently supported:
+* Ubuntu Linux 14.04 with GCC 4.9.x
+* Ubuntu Linux 16.04 with GCC 5.4.x
+* [C++11 standard](https://github.com/smartdevicelink/sdl_evolution/issues/132)
+
### Issues
If writing a bug report, please make sure <a href="http://yourbugreportneedsmore.info" target="_blank">it has enough info</a>. Include all relevant information.