Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:112311 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 33020 invoked from network); 28 Nov 2020 12:17:12 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 Nov 2020 12:17:12 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0F72F1804D1 for ; Sat, 28 Nov 2020 03:43:52 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_20,HTML_MESSAGE, SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-mahalux.mvorisek.com (mail-mahalux.mvorisek.com [77.93.195.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 28 Nov 2020 03:43:50 -0800 (PST) Received: from a993c02b797f (10.228.0.252) by mail-mahalux.mvorisek.com (10.228.0.4) with Microsoft SMTP Server (TLS); Sat, 28 Nov 2020 12:43:47 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_649b3b5cd995583738e03020754105a7" Date: Sat, 28 Nov 2020 12:43:46 +0100 To: internals@lists.php.net Message-ID: <8caf76f8d4374cde64343132fa8f2ba1d0debe7a5bc4a05f346f67fdabe499f7@mahalux.com> X-Mailer: SAP NetWeaver 7.03 Subject: Nightly builds From: vorismi3@fel.cvut.cz (=?UTF-8?Q?Michael_Vo=C5=99=C3=AD=C5=A1ek_-_=C4=8CVUT_FEL?=) --=_649b3b5cd995583738e03020754105a7 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed Hi internals, currently, as far as I know, php does not have nightly builds. By nighly I means builds/releases that are tested to pass all CI tests. This is not the case with master branch, as that branch can be failing tests. I propose to introduce "nightly" branch that will point to "the latest master head that passed all CI tests". To limit cache misses on dependent projects/builds (like docker images), I propose to update "nightly" branch no more than once per day. This will allow php comunity reliable testing of new language/engine features much more sooned until next php minor version has an alpha release. What is your opinion on this and is here someone that can implement it? With kind regards / Mit freundlichen Grüßen / S přátelským pozdravem, Michael Voříšek ČVUT FEL --=_649b3b5cd995583738e03020754105a7--