|
Size: 161
Comment: page layout
|
Size: 2215
Comment: re-organize links relating to release management
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Sage Development = | Welcome to the '''Sage developer center'''! |
| Line 3: | Line 3: |
| This wiki page helps in organizing the development of Sage. Information and links to Sage development should be organized under "dev/". | This wiki page helps in organizing the development of Sage. Information and links to Sage development should be organized under "devel/". For answers to commonly asked questions, see the [[faq | FAQ]]. Note: The [[http://trac.sagemath.org/sage_trac/ |trac server]] contains patches awaiting review. Michael Abshoff wrote a set of [[devel/TracGuidelines | general guidelines]] for using the trac server. See also the [[http://www.sagemath.org/doc/developer/trac.html | Developers' Guide]] for further information on using the trac patch server. <<TableOfContents>> = Release management = Each release cycle of Sage is managed by at least one release manager. For example, a release manager produces the various alpha and rc releases for the `sage-x.y.z` release cycle. Release management is a complex task. The [[release | release management]] page contains a rough set of guidelines for Sage release management. If you want to help out with release management, please subscribe to the [[http://groups.google.com/group/sage-release | sage-release]] mailing list. * [[SageClusterGuidelines | Sage cluster guidelines]] --- guidelines for using machines on the Sage cluster * [[UpdateCopyright | Update the copyright notice]] * [[Software | Ideas for software to integrate with Sage]] * [[Software_that_may_be_useful | Software that may be useful]] * [[SEP | Sage Enhancement Proposals]] * [[Software_surveys | Software surveys]] * [[DebianSAGE | Sage in Debian]] * [[HowToBeginSageDevelopment | How to begin Sage development]] * [[devel/nonASCII | non-ASCII characters]] in source files * [[firefox-trac | Cool tricks]] for better Firefox/trac integration * [[combinat/HelpOnTheDoc | Docstring documentation]] for help on the format (ReSTructured text) used in the docstrings, including special Sage doctest conventions * [[JavascriptResources | JavaScript and related resources]] * [[PythonResources | Python and Cython resources]] * [[SageUsability | Sage usability improvements list]] * [[SageTasks | Sage usability task list]] * [[SageNotebook | Technical overview of the Sage notebook]] |
Welcome to the Sage developer center!
This wiki page helps in organizing the development of Sage. Information and links to Sage development should be organized under "devel/". For answers to commonly asked questions, see the FAQ.
Note: The trac server contains patches awaiting review. Michael Abshoff wrote a set of general guidelines for using the trac server. See also the Developers' Guide for further information on using the trac patch server.
Contents
Release management
Each release cycle of Sage is managed by at least one release manager. For example, a release manager produces the various alpha and rc releases for the sage-x.y.z release cycle. Release management is a complex task. The release management page contains a rough set of guidelines for Sage release management. If you want to help out with release management, please subscribe to the sage-release mailing list.
Sage cluster guidelines --- guidelines for using machines on the Sage cluster
non-ASCII characters in source files
Cool tricks for better Firefox/trac integration
Docstring documentation for help on the format (ReSTructured text) used in the docstrings, including special Sage doctest conventions