Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120113
Feedback-ID: id4f946ef:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-372-g43825cb665-fm-20230411.003-g43825cb6
Mime-Version: 1.0
Message-ID: <5e54ca80-efb2-4a53-8286-1c119ec4179c@app.fastmail.com>
In-Reply-To: <90094848-cf18-1b41-da8d-1abd60461940@gmx.de>
References: <90094848-cf18-1b41-da8d-1abd60461940@gmx.de>
Date: Sun, 23 Apr 2023 22:32:13 +0200
To: internals@lists.php.net
Content-Type: multipart/alternative;
 boundary=58ee65893efa42fe91f102327d5614e8
Subject: Re: [PHP-DEV] Windows PECL build machine died
From: langemeijer@php.net ("Casper Langemeijer")

--58ee65893efa42fe91f102327d5614e8
Content-Type: text/plain

Nothing seems to happen on this front, and our Windows users like to move to PHP 8.2 too.

The windows.php.net site states: "This is because the Windows PECL build machine died, and the team is still working on the long term plan of building DLLs for PECL extensions with a new CI process."

We are 1 year since the machine died. 6 month since the statement on the website. From the point of view of our users nothing has changed, and are questioning if the windows project is still alive.

I'd like to ask: Is re-inventing the building process really a smart thing to do if it means we'll be out-of-service for more than a year?

"We're doing our best to finish that as soon as possible, and keep you up to date."

I'm not questioning intentions, but I hate to think this is 'our best'. We should at least have and share a more concrete plan, possibly share a rough timeframe and share if we hit a blocking problem. If help is needed, we should ask.

Greetings, Casper
--58ee65893efa42fe91f102327d5614e8--