How to make a release

Update files

Update the NEWS.txt and move the old stuff in the HISTORY.txt file.To update the NEWS.txt file, check all ticket closed for this releaseand all commit log messages. Update the Theano/doc/index.txt News section.

Update the “Vision”/”Vision State” in the fileTheano/doc/introduction.txt.

Update the file .mailmap to clean up the list of contributor.

Get a fresh copy of the repository

Clone the code:

  1. git clone git@github.com:Theano/Theano.git Theano-0.X

It does not have to be in your PYTHONPATH.

Update the version number

Edit setup.py to contain the newest version number

  1. cd Theano-0.X
  2. vi setup.py     # Edit the MAJOR, MINOR, MICRO and SUFFIX

Theano/doc/conf.py should be updated in the following ways:

  • Change the version and release variables to new version number.
  • Change the upper copyright year to the current year if necessary.

Update the year in the Theano/LICENSE.txt file too, if necessary.

NEWS.txt usually contains the name and date of the release, change themtoo.

Update the code and the documentation for the theano flagswarn.ignore_bug_before to accept the new version. You must modify thefile theano/configdefaults.py and doc/library/config.txt.

Tag the release

You will need to commit the previous changes, tag the resulting version, andpush that into the original repository. The syntax is something like thefollowing:

  1. git commit -m "Modifications for 0.X.Y release" setup.py doc/conf.py NEWS.txt HISTORY.txt theano/configdefaults.py doc/library/config.txt
  2. git tag -a rel-0.X.Y
  3. git push
  4. git push --tags

The documentation will be automatically regenerated in the next few hours.

Generate and upload the package

On PyPI

Set your umask to 0022 to ensure that the package file will be readable from other people.To check your umask:

  1. umask

To set your umask:

  1. umask 0022

Now change ISRELEASED in setup.py to True.

Finally, use setuptools to register and upload the release:

  1. python setup.py register sdist --formats=gztar,zip upload

This command register and uploads the package on pypi.python.org. To be ableto do that, you must register on PyPI (you can create an new account, or useOpenID), and be listed among the “Package Index Owners” of Theano.

There is a bug in some versions of distutils that raises aUnicodeDecodeError if there are non-ASCII characters in NEWS.txt. Youwould need to change NEWS.txt so it contains only ASCII characters (theproblem usually comes from diacritics in people’s names).

On mloss.org (for final releases only)

Project page is at http://mloss.org/software/view/241/.Account jaberg is listed as submitter.

  • log in as jaberg to mloss
  • search for theano and click the logo
  • press ‘update this project’ on the left and change
  • the version number
  • the download link
  • the description of what has changed
  • press save Make sure the “what’s changed” text isn’t too long because it will show up onthe front page of mloss. You have to indent bullet lines by 4 spaces I think inthe description.

You can “update this project” and save lots of times to get the revision textright. Just do not change the version number.

Finally

Change ISRELEASED back to False.

Update documentation server scripts

The documentation server runs the auto-generation script regularly. Itcompiles the latest development version and puts it in$webroot/theano_versions/dev/. It then checks if the release branchhas been updated and if it has, the release documentation is updated andput into $webroot/theano/. Finally, it checks for archived versions in$webroot/theano_versions/ and generates a versions.json fileon the server that is used to populate the version switcher.

If the release branch has changed, you must update the web server script.Login to the deeplearning.net server as the user in charge ofdocument generation. In the shell script ~/bin/updatedocs, update thevariable release to the branch name for the current release.

You can also add previous releases to the versions documentation archive.In the script ~/bin/updatedocs_versions, change the variableVersions to the git tag of the documentation version to generate,then run the script.

Announce the release

Generate an e-mail from the template in EMAIL.txt, including contentfrom NEWS.txt.

For final releases, send the e-mail to the following mailing lists:

For release candidates, only e-mail:

  • theano-announce
  • theano-dev
  • theano-users

For alpha and beta releases, only e-mail:

  • theano-dev
  • theano-users