From pd@|gd @end|ng |rom gm@||@com  Mon Jun  8 09:08:20 2020
From: pd@|gd @end|ng |rom gm@||@com (peter dalgaard)
Date: Mon, 8 Jun 2020 09:08:20 +0200
Subject: [Rd] 
 [External] Re: use of the tcltk package crashes R 4.0.1 for Windows
In-Reply-To: <CAB8pepwjyyfa63KkUKsCGOpoVQjcT10+g1Rc0BSv_zQ8b8NRow@mail.gmail.com>
References: <ACD1644AA6C67E4FBD0C350625508EC88CF55DA3@FHSDB2D11-2.csu.mcmaster.ca>
 <CABFfbXuT+hs2uAQuGtvJ_-c1xQPwx6Z+kfiUUwHJkvd4jzY6dg@mail.gmail.com>
 <B39BE746-8080-416C-A5C9-A1E6F06BA7BC@gmail.com>
 <alpine.DEB.2.21.2006071040370.3474@luke-Latitude-7480>
 <ACD1644AA6C67E4FBD0C350625508EC88CF58511@FHSDB2D11-2.csu.mcmaster.ca>
 <CAB8pepw4B9EDbbxuqb0Bu9RddjTw1LeeaQK63qw7O36dxwGwSg@mail.gmail.com>
 <CAB8pepwjyyfa63KkUKsCGOpoVQjcT10+g1Rc0BSv_zQ8b8NRow@mail.gmail.com>
Message-ID: <E91D5B42-F4D1-418D-BB4A-7D1D34E332CD@gmail.com>

Well...

The first rule of release management is not to have the same version number on different releases.

I see three possibilities

(1) Tell users to use 4.0.1-patched if they need tcltk on Windows
(2) A "vendor patch release": Windows maintainer reissues the binary after applying the critical patch. 
(3) 4.0.2 As soon as possible (realistically June 22nd-ish)

Now, (1) requires no intervention, but it has the problem that we are approaching the time for campus-wide installations (insofar as campuses will actually reopen in Fall). It will be messy to have to tell IT not to use the officially released binary, and most likely they just won't.

(2) is possible if we act quickly, although it leaves a "ghost version" of 4.0.1 around (and don't try renaming tricks, it can mess up CRAN scripts - some of us have the scars...). It should work but it is a bit iffy because the actual problem is in fact in the sources and it creates a situation where the binary and the sources are out of sync.

(3) is clean, but it takes a while (minimum 12 days) to go through the release run-in. Also, for a new release, I suspect we want to have a closer look at the issue as we seem to be using multiple allocators on Windows in a, hmmm, "eclectic mix". (E.g. connections.c has both Calloc/Free and malloc/free combinations and AFAICT, the latter uses a different allocator.)  

-pd


> On 8 Jun 2020, at 01:20 , Abby Spurdle <spurdle.a at gmail.com> wrote:
> 
> sorry, release "versions"
> 
> 
> On Mon, Jun 8, 2020 at 11:17 AM Abby Spurdle <spurdle.a at gmail.com> wrote:
>> 
>> On Mon, Jun 8, 2020 at 4:09 AM Fox, John <jfox at mcmaster.ca> wrote:
>>> Does it make sense to withdraw the Windows R 4.0.1 binary until the issue is resolved?
>> 
>> Yes, it does.
>> All the release reversions should be removed.

-- 
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: pd.mes at cbs.dk  Priv: PDalgd at gmail.com



[Rd] [External] Re: use of the tcltk package crashes R 4.0.1 for Windows
peter dalgaard