On 22.04.2020 13:06, Nathan Hartman wrote:
> On Wed, Apr 22, 2020 at 3:13 AM Stefan Sperling <stsp_at_elego.de
> <mailto:stsp_at_elego.de>> wrote:
> The current prospected release date for 1.14 is May 6, which is no
> viable. The official soak period (which starts today) does not
> allow for
> a release this soon. We will also need to allocate at least
> another week
> to collect new signatures for the final release artifacts once
> they have
> become available.
> So if we stick to the official plan, provided we don't discover
> any major
> problems during the soak period, we can prepare 1.14.0 on the 20th
> of May
> and probably release on the 27th of May.
> Is this OK or would anyone prefer to expedite this process (e.g. by
> shortening the soak period)?
> This being a LTS .0 release, I think we should stick to the official
> soak as documented, unless someone has a really compelling reason to
> do otherwise.
> But perhaps we could try to save the extra week (May 20-27) by
> parallel processing: If no showstoppers are found by May 13th, we
> could optimistically begin testing / signing of the rebranded release
> artifacts; if on May 20th no showstoppers were found in -rc2 and the
> required signatures are collected, then we could release immediately.
> My only concern with this "parallel processing" approach is the risk
> of confusion that could arise if we did discover some major issue in
> the final week.
Also, I think we should consider getting the Python 3 fixes for Windows
into the release. They're only related to bindings and tests, so I don't
foresee any showstoppers.
On the other hand, waiting for .1 for that wouldn't be terrible.
Received on 2020-04-22 13:11:03 CEST