On Thu, Mar 6, 2008 at 11:59 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Mar 7, 8:53 am, Timothy Clemans <[EMAIL PROTECTED]> wrote: > > Does one just add a bunch of documentation and make a patch and submit > > it? Or does one make a bunch of Trac tickets and make a ton of > > patches? > > > > The idea is to add doctests. One would add doctests to one file or > directory of files and then open a ticket with a patch attached. We > don't need loads of open tickets about missing doctests since someone > has written them. "-coverage" let's you find out instantly where the > problem areas are.
Also, like all new patches in Sage, the new docstrings will be refereed, and will have to satisfy the referee. Fortunately, refereeing helps a lot in this regards. So you add doctests to a file or files, make a patch, post it to trac, and put [with patch; needs review] at the beginning of the ticket title. -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
