Bump version and run towncrier for 0.11.0 release

Author: oremanj

docs/source/history.rst

@@ -5,6 +5,99 @@ Release history
 
 .. towncrier release notes start
 
+trio-asyncio 0.11.0 (2020-03-09)
+--------------------------------
+
+Features
+~~~~~~~~
+
+- Substantially reorganize monkeypatching for asyncio event loop and
+  event loop policy accessors, fixing support for Python 3.8. Also, stop
+  using features deprecated in Trio 0.12. (`#66 <https://github.com/python-trio/trio-asyncio/issues/66>`__)
+
+Bugfixes
+~~~~~~~~
+
+- Calling ``loop.stop`` manually no longer causes a deadlock when
+  exiting the context of ``trio_asyncio.open_loop`` (`#58 <https://github.com/python-trio/trio-asyncio/issues/58>`__)
+
+Deprecations and Removals
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- The non-underscore-prefixed names of trio-asyncio submodules (``trio_asyncio.loop``,
+  ``trio_asyncio.adapter``, etc) have been deprecated; public names should be
+  imported from ``trio_asyncio`` directly.
+
+  ``trio_asyncio.current_policy``, ``trio_asyncio.TrioChildWatcher``,
+  and ``trio_asyncio.TrioPolicy`` have been deprecated with no
+  replacement.  ``current_policy`` is no longer used at all, and the
+  other two are singletons that can't be customized so there's no reason
+  to make them publicly visible.
+
+  A number of functions which were already documented as deprecated now
+  raise the new :exc:`~trio_asyncio.TrioAsyncioDeprecationWarning` where
+  previously they provided either no runtime warning or a generic
+  :exc:`DeprecationWarning`. (`#64 <https://github.com/python-trio/trio-asyncio/issues/64>`__)
+
+trio-asyncio 0.10.0 (2018-12-09)
+--------------------------------
+
+Bugfixes
+~~~~~~~~
+
+- Replace deprecated ``trio.Queue`` with new channels, requiring Trio 0.9 or later. (`#49 <https://github.com/python-trio/trio-asyncio/issues/49>`__)
+
+trio-asyncio 0.9.1 (2018-09-06)
+-------------------------------
+
+Features
+~~~~~~~~
+
+- **Major reorganization:** The main entry point for calling asyncio
+  from trio is now the :func:`trio_asyncio.aio_as_trio` adapter.
+  Instead of calling :func:`asyncio.get_event_loop`, directly access the
+  contextvar ``trio_aio_loop`` (aka :var:`trio_asyncio.adapter.current_loop`). (`#36 <https://github.com/python-trio/trio-asyncio/issues/36>`__)
+
+Bugfixes
+~~~~~~~~
+
+- Defer creating an asyncio coroutine until asyncio mode is actually entered. (`#40 <https://github.com/python-trio/trio-asyncio/issues/40>`__)
+
+Deprecations and Removals
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- ``run_asyncio()`` is deprecated: replace with a :func:`aio_as_trio` wrapper.
+
+  ``trio2aio()`` is deprecated: replace with :func:`aio_as_trio`.
+
+  ``run_future()`` and ``TrioEventLoop.run_future()`` are deprecated:
+  replace with :func:`run_aio_future`.
+
+  ``run_coroutine()`` and ``TrioEventLoop.run_coroutine()`` are
+  deprecated: replace with :func:`run_aio_coroutine`.
+
+  ``TrioEventLoop.wrap_generator()`` is deprecated: replace with a
+  :func:`aio_as_trio` wrapper.
+
+  ``TrioEventLoop.run_iterator()`` is deprecated: replace with
+  :func:`aio_as_trio`. (`#36
+  <https://github.com/python-trio/trio-asyncio/issues/36>`__)
+
+trio-asyncio 0.8.4 (2018-08-25)
+-------------------------------
+
+trio-asyncio 0.8.3 (2018-08-25)
+-------------------------------
+
+trio-asyncio 0.8.2 (2018-08-25)
+-------------------------------
+
+trio-asyncio 0.8.1 (2018-08-25)
+-------------------------------
+
+trio-asyncio 0.8.0 (2018-08-03)
+-------------------------------
+
 trio-asyncio 0.8.1 (2018-08-25)
 -------------------------------
 

newsfragments/36.feature.rst

@@ -1,3 +1,3 @@
 # This file is imported from __init__.py and exec'd from setup.py
 
-__version__ = "0.10.0"
+__version__ = "0.11.0"