[pep-569] Update Beta 1, Beta 2 schedule

pep-0569.rst

@@ -50,17 +50,17 @@ Release Schedule
 Note: the dates below are not set in stone yet.  The PEP is in draft
 status.  Suggestions and comments welcome.
 
-Expected:
-
+Actual:
 - 3.8 development begins: Monday, 2018-01-29
 - 3.8.0 alpha 1: Sunday, 2019-02-03
 - 3.8.0 alpha 2: Monday, 2019-02-25
 - 3.8.0 alpha 3: Monday, 2019-03-25
 - 3.8.0 alpha 4: Monday, 2019-05-06
-- 3.8.0 beta 1: Friday, 2019-05-31
+- 3.8.0 beta 1: Tuesday, 2019-06-04
   (No new features beyond this point.)
 
-- 3.8.0 beta 2: Monday, 2019-06-24
+Expected:
+- 3.8.0 beta 2: Monday, 2019-07-01
 - 3.8.0 beta 3: Monday, 2019-07-29
 - 3.8.0 beta 4: Monday, 2019-08-26
 - 3.8.0 candidate 1: Monday, 2019-09-30
@@ -73,10 +73,28 @@ Subsequent bugfix releases at a monthly cadence.
 Features for 3.8
 ================
 
-Implemented changes for 3.8 (as of May 6th 2019):
+Some of the notable features of Python 3.8 include:
 
 * PEP 572, Assignment Expressions
 * PEP 570, Positional-only arguments
+* PEP 587, Python Initialization Configuration
+* PEP 590, Vectorcall: a fast calling protocol for CPython
+* Parallel filesystem cache for compiled bytecode
+* Debug builds share ABI as release builds
+* f-strings support a handy ``=`` specifier for debugging
+* ``continue`` is now legal in ``finally:`` blocks
+* on Windows, the default ``asyncio`` event loop is now
+  ``ProactorEventLoop``
+* on macOS, the *spawn* start method is now used by default in
+  ``multiprocessing``
+* ``multiprocessing`` can now use shared memory segments to avoid
+  pickling costs between processes
+* ``typed_ast`` is merged back to CPython
+* ``LOAD_GLOBAL`` is now 40% faster
+* ``pickle`` now uses Protocol 4 by default, improving performance
+
+There are many other interesting changes, please consult the
+"What's New" page in the documentation for a full list.
 
 
 Copyright