summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Ivanov <pi@berkeley.edu>2013-04-08 16:35:15 -0700
committerPaul Ivanov <pi@berkeley.edu>2013-04-08 16:43:56 -0700
commit7fe071ceed336b0e118c384c8ae6e469faa50102 (patch)
tree27b13a18332fda55782f6127d17d4deff6c81124
parentf85bdf48aadf7b5a5f575370b589805fed190a6c (diff)
downloadnumpy-7fe071ceed336b0e118c384c8ae6e469faa50102.tar.gz
DOC: point to the github issues page
-rw-r--r--doc/source/about.rst4
-rw-r--r--doc/source/bugs.rst20
2 files changed, 11 insertions, 13 deletions
diff --git a/doc/source/about.rst b/doc/source/about.rst
index bcfbe5323..a4a3f21d2 100644
--- a/doc/source/about.rst
+++ b/doc/source/about.rst
@@ -36,7 +36,9 @@ Our main means of communication are:
- `Mailing lists <http://scipy.org/Mailing_Lists>`__
-- `Numpy Trac <http://projects.scipy.org/numpy>`__ (bug "tickets" go here)
+- `Numpy Issues <https://github.com/numpy/numpy/issues>`__ (bug reports go here)
+
+- `Old Numpy Trac <http://projects.scipy.org/numpy>`__ (deprecated)
More information about the development of Numpy can be found at
http://scipy.org/Developer_Zone
diff --git a/doc/source/bugs.rst b/doc/source/bugs.rst
index cd2c5d3e8..85ad62610 100644
--- a/doc/source/bugs.rst
+++ b/doc/source/bugs.rst
@@ -3,21 +3,17 @@ Reporting bugs
**************
File bug reports or feature requests, and make contributions
-(e.g. code patches), by submitting a "ticket" on the Trac pages:
+(e.g. code patches), by submitting a "ticket" on GitHub:
-- Numpy Trac: http://scipy.org/scipy/numpy
+- Numpy Issues: http://github.com/numpy/numpy/issues
-Because of spam abuse, you must create an account on our Trac in order
-to submit a ticket, then click on the "New Ticket" tab that only
-appears when you have logged in. Please give as much information as
-you can in the ticket. It is extremely useful if you can supply a
-small self-contained code snippet that reproduces the problem. Also
-specify the component, the version you are referring to and the
-milestone.
+Please give as much information as you can in the ticket. It is extremely
+useful if you can supply a small self-contained code snippet that reproduces
+the problem. Also specify the component, the version you are referring to and
+the milestone.
-Report bugs to the appropriate Trac instance (there is one for NumPy
-and a different one for SciPy). There are also read-only mailing lists
-for tracking the status of your bug ticket.
+Report bugs to the appropriate GitHub project (there is one for NumPy
+and a different one for SciPy).
More information can be found on the http://scipy.org/Developer_Zone
website.