Ticket #2258 (closed defect: fixed)
put dsage documentation into the main sage documentation
| Reported by: | yi | Owned by: | yi |
|---|---|---|---|
| Priority: | major | Milestone: | sage-2.10.3 |
| Component: | documentation | Keywords: | dsage |
| Cc: | TimothyClemans | Work issues: | |
| Report Upstream: | Reviewers: | ||
| Authors: | Merged in: | ||
| Dependencies: | Stopgaps: |
Description (last modified by mabshoff) (diff)
Currently the dsage documentation lies inside it's own module. It would be much better if it were included in the sage-doc package.
Change History
comment:3 follow-up: ↓ 4 Changed 5 years ago by yi
- Status changed from new to closed
- Resolution set to fixed
This has been resolved for 2.10.3.
comment:4 in reply to: ↑ 3 Changed 5 years ago by mabshoff
- Status changed from closed to reopened
- Resolution fixed deleted
Replying to yi:
This has been resolved for 2.10.3.
Once more: Do *not* close ticket unless William or the release manager tells you to do it. It is unclear to me which ticker and/or patch resolved this.
Michael
comment:5 follow-up: ↓ 6 Changed 5 years ago by yi
Please close this ticket because #2323 has been resolved. I will create a new ticket specifically for the reference manual.
Thanks, Yi
comment:6 in reply to: ↑ 5 Changed 5 years ago by mabshoff
- Description modified (diff)
Replying to yi:
Please close this ticket because #2323 has been resolved. I will create a new ticket specifically for the reference manual.
Thanks, Yi
Hi Yi,
that is exactly the info you need to supply to get a ticket closed. It is nothing personal, but somebody else who will looks at this ticket need to be clear immediately why it was closed, i.e. with a reference to another ticket in this case. This it is difficult to get right. I myself have closed tickets 5+ months ago and needed to look long and hard to figure out why, so I have come up with a certain workflow that seems to work well. Obviously, if you have some suggestions on how to improve things are always welcome.
Cheers,
Michael
Cheers,
Michael

You just have to edit some files in devel/doc/ref/. I've made this directory much more cleanly structured. Read the file README.txt in devel/doc/ref.
William