#8051: SageNB 0.7.2
---------------------------------------------+------------------------------
Reporter: mpatel | Owner: mpatel
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.3.2
Component: notebook | Keywords:
Author: Mitesh Patel | Upstream: N/A
Reviewer: Robert Mařík, Minh Van Nguyen | Merged:
Work_issues: |
---------------------------------------------+------------------------------
Comment(by mvngu):
Replying to [comment:18 acleone]:
> Is there a mailing list or wiki page for coordinating development
effort?
A relevant mailing is [http://groups.google.com/group/sage-devel sage-
devel]. Most of the time, that list receives high volume traffic on
development discussion. For coordinating release effort, the
[http://groups.google.com/group/sage-release sage-release] mailing list is
appropriate. Some effort is underway to expand the Sage documentation with
information to help beginners getting started with Sage development. The
relevant tickets are:
1. #8108: Expand the Sage Developer Guide for newcomers
1. #6987: reorganize section on producing patches with Mercurial
1. #8079: Better documentation for patching spgk's
1. #8104: developer's guide for making spkgs should specify that patches
need to be version controlled
1. #3882: explain in the programming guide why spkg source patches should
be applied by copying entire files
1. #7944: update Developers' Guide to reflect new process for working on
tickets
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8051#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.
