From: Guenter M. <mi...@us...> - 2022-06-13 20:43:37
|
On 2022-06-12, Adam Turner wrote: >> maybe I am able to ship 0.19.0b1 on tuesday (tuesday is release day) The first in a series of beta releases should be release level = "beta", serial = 0, release = True. https://docutils.sourceforge.io/docs/dev/policies.html#docutils-version The upcoming release would then have ``__version__ = '0.19b'`` (or "0.19.0b0") rsp. ``__version_info__ = (0, 19, 0, 'beta', 0, True)``. >> june 14 or waiting for 450 on 21. > Brilliant, thanks Engelbert! I will wait for Günter's response on > bugs#450, but probably the 21st is the best option, The last patch for the problem described in bug #450 is "minimally invasive" but still an incompatible API change. https://sourceforge.net/p/docutils/bugs/450/#937a/460a/81bc/e203/ecc3/c6b8 I am still unsure whether curing an announced incompatible API change with an unannounced one is the right way. I would prefer announcing in 0.19 and changing in 0.20 but can also live with an unannounced fix, if this is considered the lesser evil. (We still don't know, whether the fix would satisfy the OP.) > with 0.19.0 final then released on 05/07. We have done some large changes and some removals, so maybe a longer beta period is appropriate... Günter |