#6226: [with patch, needs review] developer's guide: sections on formatting
docstrings and trac guidelines
---------------------------+------------------------------------------------
 Reporter:  mvngu          |       Owner:  tba              
     Type:  enhancement    |      Status:  new              
 Priority:  major          |   Milestone:  sage-4.0.1       
Component:  documentation  |    Keywords:  developer's guide
---------------------------+------------------------------------------------

Comment(by jhpalmieri):

 Comments: very nice overall.  I have a second patch, to be applied on top
 of yours, which deals with a few small issues:

 in producing_patches.rst, {{{hg_sage.patch(...)}}} and
 {{{hg_sage.apply(...)}}} are not synonyms, and it sounds like that a bit.
 Also, you've deleted one reference to the "doc" repository, but there's
 another (two lines after "Sage includes these Mercuruial repositories").

 in sage_manuals.rst: as far as I can tell, you don't need to run {{{sage
 -b}}} when producing new versions of any manual other than the reference
 manual: just edit the files and run {{{sage -docbuild tutorial html}}} or
 whatever.  There are a few typos, too.

 in trac.rst: I thought that a few of the lines from the wiki were more
 appropriate for a wiki page than a formal piece of documentation, so I
 removed them.

 I give your patch a positive review, so if you're happy with mine, the
 whole thing is ready to go.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6226#comment:2>
Sage <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to