From 37b9ee0b5744e030800250a5af96ab8ab04001dd Mon Sep 17 00:00:00 2001 From: Anas Nashif Date: Mon, 2 Oct 2017 22:33:16 -0400 Subject: [PATCH] doc: reference github issues instead of jira Signed-off-by: Anas Nashif --- CONTRIBUTING.rst | 12 ++++++------ README.rst | 4 ++-- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 95878ed2cc1..87628a5fec3 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -169,14 +169,14 @@ available for developers to contribute to and enhance. Pull Requests and Issues ************************ -.. _Zephyr Project Issues: https://jira.zephyrproject.org +.. _Zephyr Project Issues: https://github.com/zephyrproject-rtos/zephyr/issues .. _open pull requests: https://github.com/zephyrproject-rtos/zephyr/pulls .. _Zephyr-devel mailing list: https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel -Before starting on a patch, first check in our Jira `Zephyr Project Issues`_ +Before starting on a patch, first check in our issues `Zephyr Project Issues`_ system to see what's been reported on the issue you'd like to address. Have a conversation on the `Zephyr-devel mailing list`_ (or the #zephyrproject IRC channel on freenode.net) to see what others think of your issue (and proposed @@ -191,7 +191,7 @@ triage team will review and comment on the submission, typically within a few business days. You can find all `open pull requests`_ on GitHub and open `Zephyr Project -Issues`_ in Jira. +Issues`_ in Github issues. Development Tools and Git Setup ******************************* @@ -316,7 +316,7 @@ workflow here: $ git remote -v #. Create a topic branch (off of master) for your work (if you're addressing - Jira issue, we suggest including the Jira issue number in the branch name):: + an issue, we suggest including the issue number in the branch name):: $ git checkout master $ git checkout -b fix_comment_typo @@ -434,9 +434,9 @@ Changes are submitted as Git commits. Each commit message must contain: * A Signed-off-by line, ``Signed-off-by: `` typically added automatically by using ``git commit -s`` -* If the change address a Jira issue, include a line of the form:: +* If the change addresses an issue, include a line of the form:: - Jira: ZEP-xxx + Fixes #. All changes and topics sent to GitHub must be well-formed, as described above. diff --git a/README.rst b/README.rst index cb3ea997c5b..626cf4894e5 100644 --- a/README.rst +++ b/README.rst @@ -69,8 +69,8 @@ support systems: the `Zephyr GitHub wiki`_. * **Issue Reporting and Tracking**: Requirements and Issue tracking is done in - our JIRA system: https://jira.zephyrproject.org. You can browse through the - reported issues and submit issues of your own. + the Github issues system: https://github.com/zephyrproject-rtos/zephyr/issues. + You can browse through the reported issues and submit issues of your own. * **Security-related Issue Reporting**: For security-related inquiries or reporting suspected security-related bugs in the Zephyr OS, please