doc: reference github issues instead of jira
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
parent
e0c1c0aa64
commit
37b9ee0b57
2 changed files with 8 additions and 8 deletions
|
@ -169,14 +169,14 @@ available for developers to contribute to and enhance.
|
||||||
Pull Requests and Issues
|
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
|
.. _open pull requests: https://github.com/zephyrproject-rtos/zephyr/pulls
|
||||||
|
|
||||||
.. _Zephyr-devel mailing list:
|
.. _Zephyr-devel mailing list:
|
||||||
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel
|
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
|
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
|
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
|
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.
|
business days.
|
||||||
|
|
||||||
You can find all `open pull requests`_ on GitHub and open `Zephyr Project
|
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
|
Development Tools and Git Setup
|
||||||
*******************************
|
*******************************
|
||||||
|
@ -316,7 +316,7 @@ workflow here:
|
||||||
$ git remote -v
|
$ git remote -v
|
||||||
|
|
||||||
#. Create a topic branch (off of master) for your work (if you're addressing
|
#. 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 master
|
||||||
$ git checkout -b fix_comment_typo
|
$ 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: <name> <email>`` typically added
|
* A Signed-off-by line, ``Signed-off-by: <name> <email>`` typically added
|
||||||
automatically by using ``git commit -s``
|
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 #<issue number>.
|
||||||
|
|
||||||
|
|
||||||
All changes and topics sent to GitHub must be well-formed, as described above.
|
All changes and topics sent to GitHub must be well-formed, as described above.
|
||||||
|
|
|
@ -69,8 +69,8 @@ support systems:
|
||||||
the `Zephyr GitHub wiki`_.
|
the `Zephyr GitHub wiki`_.
|
||||||
|
|
||||||
* **Issue Reporting and Tracking**: Requirements and Issue tracking is done in
|
* **Issue Reporting and Tracking**: Requirements and Issue tracking is done in
|
||||||
our JIRA system: https://jira.zephyrproject.org. You can browse through the
|
the Github issues system: https://github.com/zephyrproject-rtos/zephyr/issues.
|
||||||
reported issues and submit issues of your own.
|
You can browse through the reported issues and submit issues of your own.
|
||||||
|
|
||||||
* **Security-related Issue Reporting**: For security-related inquiries or
|
* **Security-related Issue Reporting**: For security-related inquiries or
|
||||||
reporting suspected security-related bugs in the Zephyr OS, please
|
reporting suspected security-related bugs in the Zephyr OS, please
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue