Add new screenshots for release notes.x

docs/source/config/extensions/index.txt

@@ -1,108 +1,109 b''
 .. _extensions_overview:
 
 ==================
 IPython extensions
 ==================
 
 A level above configuration are IPython extensions, Python modules which modify
 the behaviour of the shell. They are referred to by an importable module name,
 and can be placed anywhere you'd normally import from, or in
 ``$IPYTHONDIR/extensions/``.
 
 Getting extensions
 ==================
 
 A few important extensions are :ref:`bundled with IPython <bundled_extensions>`.
 Others can be found on the `extensions index
 <http://wiki.ipython.org/Extensions_Index>`_ on the wiki, and installed with
 the ``%install_ext`` magic function.
 
 Using extensions
 ================
 
 To load an extension while IPython is running, use the ``%load_ext`` magic:
 
 .. sourcecode:: ipython
 
     In [1]: %load_ext myextension
 
 To load it each time IPython starts, list it in your configuration file::
 
     c.InteractiveShellApp.extensions = [
         'myextension'
     ]
 
 Writing extensions
 ==================
 
 An IPython extension is an importable Python module that has a couple of special
 functions to load and unload it. Here is a template::
 
     # myextension.py
 
     def load_ipython_extension(ipython):
         # The `ipython` argument is the currently active `InteractiveShell`
         # instance, which can be used in any way. This allows you to register
         # new magics, plugins or aliases, for example.
 
     def unload_ipython_extension(ipython):
         # If you want your extension to be unloadable, put that logic here.
 
 This :func:`load_ipython_extension` function is called after your extension is
 imported, and the currently active :class:`~IPython.core.interactiveshell.InteractiveShell`
 instance is passed as the only argument. You can do anything you want with
 IPython at that point.
 
 :func:`load_ipython_extension` will be called again if you load or reload
 the extension again. It is up to the extension author to add code to manage
 that.
 
 Useful :class:`InteractiveShell` methods include :meth:`~IPython.core.interactiveshell.InteractiveShell.define_magic`, 
 :meth:`~IPython.core.interactiveshell.InteractiveShell.push` (to add variables to the user namespace) and 
 :meth:`~IPython.core.interactiveshell.InteractiveShell.drop_by_id` (to remove variables on unloading).
 
 You can put your extension modules anywhere you want, as long as they can be
 imported by Python's standard import mechanism. However, to make it easy to
 write extensions, you can also put your extensions in
 ``os.path.join(ip.ipython_dir, 'extensions')``. This directory is added to
 ``sys.path`` automatically.
 
 When your extension is ready for general use, please add it to the `extensions
 index <http://wiki.ipython.org/Extensions_Index>`_.
 
 Plugin class
 ------------
 
 More advanced extensions might want to subclass :class:`IPython.core.plugin.Plugin`.
 A plugin can have options configured by IPython's main :ref:`configuration
 system <config_overview>`. The code to load and unload it looks like this::
 
     def load_ipython_extension(ip):
         """Load the plugin in IPython."""
         plugin = MyPlugin(shell=ip, config=ip.config)
         try:
             ip.plugin_manager.register_plugin('myplugin', plugin)
         except KeyError:
             print("Already loaded")
     
     def unload_ipython_extension(ip):
         ip.plugin_manager.unregister_plugin('myplugin')
 
 For examples, see these files:
 
 * :file:`IPython/extensions/autoreload.py`
 * :file:`IPython/extensions/storemagic.py`
 
 .. _bundled_extensions:
 
 Extensions bundled with IPython
 ===============================
 
 .. toctree::
    :maxdepth: 1
 
    autoreload
    cythonmagic
+   octavemagic
    rmagic
    storemagic
    sympyprinting

docs/source/whatsnew/development.txt

@@ -1,99 +1,6 b''
 =====================
  Development version
 =====================
 
 This document describes in-flight development work.
 
-Redesigned IPython notebook user interface
-------------------------------------------
-
-(Add description & screenshots of the many changes to the notebook)
-
-Improved tooltips
-~~~~~~~~~~~~~~~~~
-
-The object tooltips have gained some new functionality. By pressing tab several
-times, you can expand them to see more of a docstring, keep them visible as you
-fill in a function's parameters, or transfer the information to the pager at the
-bottom of the screen. For the details, look at the example notebook
-:file:`01_notebook_introduction.ipynb`.
-
-Cell magics
------------
-
-IPython's ``%magic`` functions have been extended to let you change the meaning
-of a whole cell using the first line. For example, to time the execution of
-several statements::
-
-    %%timeit x = 0   # setup
-    for i in range(100000):
-        x += i**2
-
-This is particularly useful to integrate code in another language, and cell
-magics already exist for shell scripts, Cython, R and Octave. Using ``%%script
-/usr/bin/foo``, you can run a cell in any interpreter that accepts code via
-stdin.
-
-Another handy cell magic makes it easy to write short text files: ``%%file
-~/save/to/here.txt``.
-
-To allow these features, the API for magic functions has been refactored and
-made more powerful (:ghpull:`1732`).
-
-Tab completer improvements
---------------------------
-
-Useful tab-completion based on live inspection of objects is one of the most
-popular features of IPython. To make this process even more user-friendly, the
-completers of both the Qt console and the Notebook have been reworked.
-
-The Qt console comes with a new ncurses-like tab completer, activated by
-default, which lets you cycle through the available completions by pressing tab,
-or select a completion with the arrow keys (:ghpull:`1851`).
-
-.. figure:: ../_static/ipy_o13_qtconsole_completer.png
-    :width: 400px
-    :alt: ncurses-like completer, with highlighted selection.
-    :align: center
-    :target: ../_static/ipy_o13_qtconsole_completer.png
-
-    The new improved Qt console's ncurses-like completer allows to easily
-    navigate thought long list of completions.
-
-In the notebook, completions are now sourced both from object introspection and
-analysis of surrounding code, so limited completions can be offered for
-variables defined in the current cell, or while the kernel is busy 
-(:ghpull:`1711`).
-
-Other new features
-------------------
-
-* **%install_ext**: A new magic function to install an IPython extension from
-  a URL. E.g. ``%install_ext
-  https://bitbucket.org/birkenfeld/ipython-physics/raw/default/physics.py``.
-
-* The ``%loadpy`` magic is no longer restricted to Python files, and has been
-  renamed ``%load``. The old name remains as an alias.
-
-* New command line arguments will help external programs find IPython folders:
-  ``ipython locate`` finds the user's IPython directory, and ``ipython locate
-  profile foo`` finds the folder for the 'foo' profile (if it exists).
-
-* The :envvar:`IPYTHON_DIR` environment variable, introduced in the Great
-  Reorganization of 0.11 and existing only in versions 0.11-0.13, has been
-  deprecated. As described in :ghissue:`1167`, the complexity and confusion of
-  migrating to this variable is not worth the aesthetic improvement. Please use
-  the historical :envvar:`IPYTHONDIR` environment variable instead.
-
-* The default value of *interactivity* passed from
-  :meth:`~IPython.core.interactiveshell.InteractiveShell.run_cell` to
-  :meth:`~IPython.core.interactiveshell.InteractiveShell.run_ast_nodes`
-  is now configurable.
-
-Backwards incompatible changes
-------------------------------
-
-* The exception :exc:`IPython.core.error.TryNext` previously accepted
-  arguments and keyword arguments to be passed to the next implementation
-  of the hook. This feature was removed as it made error message propagation
-  difficult and violated the principle of loose coupling.

docs/source/whatsnew/index.txt

@@ -1,33 +1,34 b''
 .. Developers should add in this file, during each release cycle, information
 .. about important changes they've made, in a summary format that's meant for
 .. end users.  For each release we normally have three sections: features,  bug
 .. fixes and api breakage.
 .. Please remember to credit the authors of the contributions by name,
 .. especially when they are new users or developers who do not regularly
 .. participate  in IPython's development.
 
 .. _whatsnew_index:
 
 =====================
 What's new in IPython
 =====================
 
 This section documents the changes that have been made in various versions of
 IPython. Users should consult these pages to learn about new features, bug
 fixes and backwards incompatibilities. Developers should summarize the
 development work they do here in a user friendly format.
 
 .. toctree::
    :maxdepth: 1
 
    development
+   version0.13
    github-stats-0.13
    version0.12
    github-stats-0.12
    version0.11
    github-stats-0.11
    version0.10
    version0.9
    version0.8