#17534: The reviewer's checklist
-----------------------------+---------------------------------
Reporter: ncohen | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.5
Component: documentation | Keywords:
Merged in: | Authors: Nathann Cohen
Reviewers: | Report Upstream: N/A
Work issues: | Branch:
Commit: | Dependencies:
Stopgaps: |
-----------------------------+---------------------------------
In the current version of the developer's manual, the section that
explains what a reviewer should check is located in the "Sage trac and
tickets" section, chapter "The Sage trac server".
http://www.sagemath.org/doc/developer/trac.html#reviewing-patches
What it explains (conventions, documentations, coverage) seems to belong
to the 'Basics of Writing and Testing Sage Code' section, and this branch
moves it there.
I also rephrased some parts of it, like in tickets #17509 and #17508, so
that you can more easily spot what you want to find.
On the way, I also created a section entitled "the status of a ticket" as
it seems that we had nothing to explain that.
Nathann
P.S.: The goal is also to have a page we could give to possible
contributors, meant to show them the way to review a ticket. For this
reason, links are provided toward other sections of the manual, like the
git commands, the conventions, etc.
--
Ticket URL: <http://trac.sagemath.org/ticket/17534>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.