Skip to content

Latest commit

 

History

History
12 lines (12 loc) · 828 Bytes

HACKING.md

File metadata and controls

12 lines (12 loc) · 828 Bytes
Raw

To create a new release

  1. assuming this repo is checked out already.
  2. bump up the version in setup.py and in 2 places in sagetex.dtx: the macro \ST@ver and inside <*latex|python> few lines above.
  3. run make with sage in the PATH, it should run without errors, and produce sagetex.pdf and example.pdf
  4. commit and push
  5. run make dist to create a tarball in dist/
  6. On github, make a new release, appropriately tagged, add there binary assets: the tarball from dist/ and the pdf files as above
  7. At this point, you are set to create Sage ticket to update the package, giving the tarball link you added as an asset.
  8. Copy the tarball to SAGEROOT/upstream/, update the checksum, create a trac git branch, etc., test that the installation of Sage package sagetex works, etc.