Newsgroups: php.internals,php.internals.win
Path: news.php.net
Xref: news.php.net php.internals:108971 php.internals.win:1220
To: Anatol Belski <ab@php.net>, PHP internals <internals@lists.php.net>,
 internals-win <internals-win@lists.php.net>
References: <df7c743d-e5b8-c588-4e85-2620f97e2356@gmx.de>
 <AM0PR0502MB3668A6EC03DE6149D76B6626C0FF0@AM0PR0502MB3668.eurprd05.prod.outlook.com>
Message-ID: <75ac8eb7-f738-b678-7348-5076f48c1260@gmx.de>
Date: Wed, 11 Mar 2020 10:53:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <AM0PR0502MB3668A6EC03DE6149D76B6626C0FF0@AM0PR0502MB3668.eurprd05.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Windows snapshot builds switching to debug
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 10.03.2020 at 13:59, Anatol Belski wrote:

> I'd see not much value in switching to debug builds for the snapshots.
> Currently the snapshots are public and are built with PGO. This makes
> it easy for users to test any provided revision. Debug builds are
> better suitable for the runtime development, but they require a debug
> runtime, can't use PGO and are in most case unusable for users.
>
> IMO, if debug builds of snapshots are needed for something, they might
> be added, but release buids of snapshots should not be removed. It is
> more important to ensure release builds, for debug they're also
> suitable in 98% of cases as it always contains debug symbols. There are
> many other points that would speak against switching to debug builds
> only. For the developer needs, debug builds can always be done on
> demand.

Thanks Anatol!  These are very valid points indeed.  I think we shall
re-consider.

It would be helpful to know who actually uses the snapshot builds, and
for which purpose.  So any feedback on that would be welcome as well.

Thanks,
Christoph