|
Size: 4885
Comment: remove outdated links
|
← Revision 40 as of 2023-02-23 20:20:48 ⇥
Size: 4248
Comment: remove Trac stuff
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| Note: Developers should check trac.sagemath.org at least one per week. That's where development actually happens. | Note: Developers should check https://github.com/sagemath/sage/issues?q=is%3Aopen+sort%3Aupdated-desc+ at least one per week. That's where development actually happens. |
| Line 32: | Line 32: |
| * [[http://trac.sagemath.org/sage_trac/|See the TRAC Server]] * [[TracGuidelines|Trac guidelines]] by Michael Abshoff |
|
| Line 41: | Line 39: |
| * [[firefox-trac|Cool tricks]] for better Firefox/trac integration | |
| Line 47: | Line 44: |
| * [[TracGuidelines|Trac guidelines]] by Michael Abshoff | |
| Line 55: | Line 51: |
| Note: The [[http://trac.sagemath.org/sage_trac/ |trac server]] contains patches awaiting review. Michael Abshoff wrote a set of [[http://www.sagemath.org/doc/developer/trac.html | 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. | |
| Line 86: | Line 81: |
| * [[firefox-trac | Cool tricks]] for better Firefox/trac integration |
Sage Developer Center
Welcome to the Sage developer center!
Note: Developers should check https://github.com/sagemath/sage/issues?q=is%3Aopen+sort%3Aupdated-desc+ at least one per week. That's where development actually happens.
TODO:
Organize, sage-devel.
Docstring Docummentation for help on the format (ReSTructured text) used in the docstrings, including special Sage doctest conventions
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.
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 development
Much of the Sage library is written in Python. Some performance critical parts of the Sage library is written in Cython. Information is available to help beginners on developing the Sage library. Also consult the list of Python and Cython resources for beginner to advanced information on the Python and Cython languages. You can also do functional programming with Python and Sage.
Please write Python3-compatible code (see Python3-compatible code) |