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 release and all commit log messages.
For the final release, copy the file Theano/NEWS.txt to Theano/doc/NEWS.txt.
Update the “Vision”/”Vision State” in the file Theano/doc/introduction.txt.
Clone the code:
git clone git@github.com:Theano/Theano.git Theano-0.X
It does not have to be in your PYTHONPATH.
Edit setup.py to contain the newest version number
cd Theano-0.X
vi setup.py # Edit the MAJOR, MINOR, MICRO and SUFFIX
conf.py in the doc/ directory 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 them too.
Update the code and the documentation for the theano flags warn.ignore_bug_before to accept the new version. You must modify the file theano/configdefaults.py and doc/library/config.txt.
You will need to commit the previous changes, tag the resulting version, and push that into the original repository. The syntax is something like the following:
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
git tag -a rel-0.X.Y
git push
git push --tags
The documentation will be automatically regenerated in the next few hours.
For release candidates, only upload on PyPI.
Now change ISRELEASED in setup.py to True.
Finally, use setuptools to register and upload the release:
python setup.py register sdist --formats=gztar,zip upload
This command register and uploads the package on pypi.python.org. To be able to do that, you must register on PyPI (you can create an new account, or use OpenID), and be listed among the “Package Index Owners” of Theano.
There is a bug in some versions of distutils that raises a UnicodeDecodeError if there are non-ASCII characters in NEWS.txt. You would need to change NEWS.txt so it contains only ASCII characters (the problem usually comes from diacritics in people’s names).
Theano project page at freshmeat is here. The package itself is not uploaded to freshmeat, the only thing to update is the description and tags.
ou can request the rights to add a release from an admin (for instance Fred), pointing them to the “roles” page. Then, create a new release from the “releases” page.
Project page is at http://mloss.org/software/view/241/. Account jaberg is listed as submitter.
- the version number
- the download link
- the description of what has changed
Make sure the “what’s changed” text isn’t too long because it will show up on the front page of mloss. You have to indent bullet lines by 4 spaces I think in the description.
You can “update this project” and save lots of times to get the revision text right. Just do not change the version number.
Change ISRELEASED back to False.
Generate an e-mail from the template in in EMAIL.txt, including content from NEWS.txt, and send it to the following mailing lists:
For release candidates, only e-mail: