|
Size: 1473
Comment: link to Developer's Guide, specifically the section about the trac server
|
Size: 2260
Comment: heading for page
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Sage Development = | = 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/". | Welcome to the '''Sage developer center'''! |
| Line 5: | Line 5: |
| ## * [:DevelopersRoom:The Developers' Room] this is totally outdated | 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]]. |
| Line 7: | Line 7: |
| * [[TracGuidelines | Trac guidelines]] by Michael Abshoff. See also the [[http://www.sagemath.org/doc/developer/trac.html | Developers' Guide]] for further information on using the trac patch server. | 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 [[devel/ReleaseManagement | 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. |
| Line 10: | Line 17: |
| Line 11: | Line 19: |
| Line 12: | Line 21: |
| Line 13: | Line 23: |
| * [[release | Release management]] | |
| Line 15: | Line 25: |
| Line 16: | Line 27: |
| Line 17: | Line 29: |
| Line 18: | Line 31: |
* [[devel/nonASCII | non-ASCII characters]] in source files |
|
| Line 19: | Line 35: |
| Line 20: | Line 37: |
| Line 21: | Line 39: |
| Line 22: | Line 41: |
| Line 23: | Line 43: |
| Line 24: | Line 45: |
Sage developer center
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