Release 2.23.0

- [FEATURE] IETF Client 0-RTT support.
- [BUGFIX] Do not schedule MTU probe on first tick.
- [BUGFIX] Parsing DATAGRAM frame.
- [BUGFIX] If push promise fails, do not invoke hset destructor.
- [BUGFIX] Client: When connections are IDed by port number, check DCID.
  Fixes issue #176.
- Revert the 2.22.1 lsquic_is_valid_hs_packet change.  All that was
  necessary is a change to the way we call it in lsquic_engine.  No
  change to the function itself is required.

docs/apiref.rst

@@ -58,9 +58,9 @@ developed by the IETF.  Both types are included in a single enum:
 
         IETF QUIC version ID 29
 
-    .. member:: LSQVER_ID30; this version is deprecated.
+    .. member:: LSQVER_ID30
 
-        IETF QUIC version ID 30
+        IETF QUIC version ID 30; this version is deprecated.
 
     .. member:: LSQVER_ID31
 

docs/conf.py

@@ -24,9 +24,9 @@ copyright = u'2020, LiteSpeed Technologies'
 author = u'LiteSpeed Technologies'
 
 # The short X.Y version
-version = u'2.22'
+version = u'2.23'
 # The full version, including alpha/beta/rc tags
-release = u'2.22.1'
+release = u'2.23.0'
 
 
 # -- General configuration ---------------------------------------------------

docs/faq.rst

@@ -18,7 +18,7 @@ connections.
 
 To aid development, there is a :macro:`LSQUIC_FORCED_TCID0_VERSIONS` that
 specifies the list of versions with 0-sized connections.  (If you, for
-example, want to turn them.)
+example, want to turn them off.)
 
 Once gQUIC becomes deprecated in the future, there will remain no technical
 reason why a single engine instance could not be used both for client and