#10118: upgrade sphinx to version 1.0.4
-------------------------------+--------------------------------------------
Reporter: mvngu | Owner: tbd
Type: enhancement | Status: needs_review
Priority: blocker | Milestone: sage-4.6.1
Component: packages | Keywords: sphinx spkg
Author: Minh Van Nguyen | Upstream: N/A
Reviewer: Jeroen Demeyer | Merged:
Work_issues: |
-------------------------------+--------------------------------------------
Comment(by jhpalmieri):
Replying to [comment:18 jdemeyer]:
> Replying to [comment:17 jhpalmieri]:
> > I don't think this is the usual practice for spkgs.
>
> I agree that this is not the usual practice, but maybe we should make it
usual practice?
I'm not sure. I hope other people express opinions. Is it worth
discussing on sage-devel? Anyway, since it's not the usual practice, I
think you should definitely document what you're doing in SPKG.txt. When
I'm working on an spkg, in general I find it very helpful to have long
descriptions in SPKG.txt, not just very short summaries of what happened.
(I'm also not sure why "patches/Makefile" has an entry in the patch file,
since this file is now supposed to be untracked.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10118#comment:19>
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 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.
