##// END OF EJS Templates
upstream » ipython
RSS

Clone from https://github.com/ipython/ipython.git

Merging Fernando's trunk (fp-trunk-dev) and Brian's edits (fp-review)....
Merging Fernando's trunk (fp-trunk-dev) and Brian's edits (fp-review). This is a huge merge of months worth of work by Fernando and Brian. Some highlights: * The test suite has been ported to use the new APIs. * The test suite runs and passes on all platforms!!! * The IPython Sphinx directive has been updated to use the new APIs. * %history works again. * New %tb magic for showing last traceback. * Significant design improvements in the config loaders and applications. * Zillions of bugs fixed. * Completely new %pylab implementation that uses the new GUI support. This allows pylab to be enabled *at runtime*. * Many other things.
Brian Granger - - Load All Authors

File last commit:

r2277:dc983636
r2515:08ca9176 merge
Show More
release.txt
31 lines | 1.3 KiB | text/plain | TextLexer
/ docs / source / development / release.txt
History | Annotation | Raw |Copy content |Copy permalink
.. _releasing_ipython:
=================
Releasing IPython
=================
This section contains notes about the process that is used to release IPython.
Our release process is currently not very formal and could be improved.
Most of the release process is automated by the :file:`release` script in the
:file:`tools` directory. This is just a handy reminder for the release manager.
#. First, run :file:`build_release`, which does all the file checking and
building that the real release script will do. This will let you do test
installations, check that the build procedure runs OK, etc. You may want to
disable a few things like multi-version RPM building while testing, because
otherwise the build takes really long.
#. Run the release script, which makes the tar.gz, eggs and Win32 .exe
installer. It posts them to the site and registers the release with PyPI.
#. Update the website with announcements and links to the updated changes.txt
in html form. Remember to put a short note both on the news page of the
site and on Launcphad.
#. Drafting a short release announcement with i) highlights and ii) a link to
the html version of the :ref:`Whats new <whatsnew_index>` section of the
documentation.
#. Make sure that the released version of the docs is live on the site.
#. Celebrate!