ReleaseInstr.md

Steps to create a Sagenb package

Throughout the steps below, replace <version> with the actual version, for example, 0.10.8.3. Also, we will assume that github.org/sagemath/sagenb is present as upstream remote repository in your local SAGENB_ROOT.

1. It wouldn't hurt to make sure the notebook actually runs before you start, or alerting to any major changes needed in localizations, either.

2. Any new or updated dependencies should be corrected in the file setup.py.

3. Change into the sagenb git directory, and update to the latest upstream/master. We assume that all the required merges to the upstream/master have happened already and that your master is at a previous or current commit (same hash) of upstream/master; if not, use git merge upstream/master instead of git rebase.

   cd SAGENB_ROOT
   git checkout master
   git fetch upstream
   git rebase upstream/master  

4. Edit Changes file to highlight the main changes. Edit setup.py to update the version for Sagenb (this is important). Example diff:

   --- a/setup.py
   +++ b/setup.py
   @@ -44,7 +44,7 @@ if __name__ == '__main__':
            distutils.log.set_threshold(distutils.log.DEBUG)
   
        code = setup(name = 'sagenb',
   -          version     = '0.10.8.2',
   +          version     = '0.10.8.3',
              description = 'The Sage Notebook',
              license     = 'GNU General Public License (GPL) v3+',
              author      = 'William Stein et al.',                      

5. Commit the updated version change.

   git add Changes
   git add setup.py
   git commit -m "Update Sagenb version to <version>"

6. Create the sagenb tarball:

   ./dist.sh

7. Let Sage know about the new sagenb and update its checksums, and then try out the new sagenb and test it. Here we are not yet committing, in case of any errors.

   cd SAGE_ROOT
   echo "<version>" > build/pkgs/sagenb/package-version.txt
   ./sage --fix-pkg-checksums
   ./sage -tp --long --sagenb  # test sagenb
   make ptestlong              # test sage

   If you are not using your sagenb repository directly inside Sage as described in the file HACKING.rst, you may need to use the following command before actually testing it out.

   ./sage -f sagenb  # if necessary to install the new sagenb

8. (Optional) Check that the Selenium tests pass.

9. (Optional) If you encounter errors or realize there was a mistake, you can try to fix them back in sagenb, after reverting the last change (the updated sagenb version).

   cd SAGENB_ROOT
   git reset --mixed  HEAD^
   <fix whatever needs fixing>
   <perhaps run tests again, from SAGE_ROOT>
   <set up changes with git add>
   git commit -m 'Fix doctests' # or whatever is appropriate
   <edit Changes and setup.py again if necessary>
   git add Changes
   git add setup.py
   git commit

   Now return to the previous steps for creating the distribution and new tar files, update checksums etc. as needed, and then proceed.

10. Now we can create a branch for the ticket <ticket>, commit our changes, and push to Trac. Warning: do not use git commit -a unless you are sure (see git status) that you don't have anything else in your directory that shouldn't be added; otherwise do git add the correct files first.

    git checkout develop -b ticket/<ticket> # or "git trac create" or "git trac checkout", etc
    git commit -a -m "Upgrade sagenb to version <version>"
    ./sage -tp --long --sagenb  # test sagenb again
    make ptestlong              # test sage again if need be
    git trac push <ticket>

    You will want to upload the sagenb tar.bz2 file somewhere convenient and put a link to it on the appropriate Trac ticket as well.

11. Now that everything is fine, update the sagenb in Github with the new changes.

    cd SAGENB_ROOT
    git tag <version>
    git push upstream master
    git checkout release
    git merge <version>
    git push upstream release
    git push upstream --tags  # This will automatically create sagenb.tar.gz in Github