SageMath Development on SageMathCloud

These are instructions on how to quickly (ie., in a few minutes) get started with Sage development on SageMathCloud.

1. Open the SMC project that you intend to use for development, or create a new project. Send an email with THE LINK TO YOUR PROJECT (under Settings) to [email protected] and say that you are using this project for legit Sage development. Wait for the reply before continuing.

2. Create an ssh key and upload the ssh key to the Sage trac server:

   • generate an ssh key using the command ssh-keygen (for more details, see Manually generating your ssh keys in the Sage Developer's Guide)

   • upload your ssh key to the trac server following ONLY ONE of these two instructions:

     • Generating and uploading your ssh keys
     • Manually linking your public key to your trac account

3. Copy the pre-compiled development version from the public project Sage Development Images.

   • Click on the "i" to the left of the directory sage-6.8.beta3, then select "Copy to another project". (For more information and to troubleshoot any problems, read the file called README.md in that project.
   • A notification will appear that the copying has started. It should take about 3 minutes to complete, but it may take longer. So take a 5 minute break. You deserve it. (Note: You will not see a notification when the copying is done.)

4. Switch to newly created Sage development directory:

    cd sage-dev-images/sage-6.8.beta3
   

   Note: At this point, running ./sage will launch the development version.

5. Add your trac account username and password:

    git trac config --user username --pass 'password'
   

   Note: You will have to do this once each time you do step 3 above.

6. Checkout a ticket, that is, switch to a new branch:

    git trac checkout 18628
   

   Note: Make sure to do step 4 first!

7. Recompile Sage:

    make start
   

   Note: this might take some time if it's an old ticket.

8. Do some development or reviewing....

   • edit some files, then 'add' them, e.g., by running git add .
   • test changes, e.g., by running ./sage -br
   • 'commit' changes, e.g., git commit -m "added 'super_conjugate' method to partition.py"
   • push your changes: git trac push

9. Go home:

    git checkout develop
   

   Note: this will bring you back to the development version of Sage without any of your modifications.

10. Return to step 6 with another ticket!

Notes:

• If you want to use the development version of Sage in your worksheets, then first run the following commands

    mkdir -p ~/bin
    cd ~/bin
    ln -sf ~/sage-dev-images/sage-6.8.beta3/sage .
  

  and then restart your worksheet server (in project settings). For details, see this entry in the FAQ.

• For more information about the general Sage development process, see the Sage Developer's Guide).

• For more information about the git trac command, see Collaborative Development with Git-Trac