Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86702
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADNQb0WrZ5nAFjNKi6935pd-JabiWTQzs56G_Q1QaEzL3rV9iw@mail.gmail.com>
References: <CADNQb0VcfzJ7U+_2t99vxpdXRSEAeHG98eAdMDB+9EOF0=rAXg@mail.gmail.com>
	<00c501d0a773$f84fee90$e8efcbb0$@belski.net>
	<CADNQb0WOx8mcrmBdofrZ4CqMJHJrdmb6oQnJTQqxmrHYLq5Xqw@mail.gmail.com>
	<557EDF48.9000800@gmx.de>
	<1434379932.17693.5.camel@kuechenschabe>
	<012e01d0a781$4f4a17e0$edde47a0$@belski.net>
	<CADNQb0WrZ5nAFjNKi6935pd-JabiWTQzs56G_Q1QaEzL3rV9iw@mail.gmail.com>
Date: Tue, 16 Jun 2015 07:39:35 +0700
Message-ID: <CAEZPtU6G77zow-ge-XOe_c7BFDNC3GVBKTzA+vpQB_xE3Evbsg@mail.gmail.com>
To: Hannes Magnusson <hannes.magnusson@gmail.com>
Cc: Christoph Becker <cmbecker69@gmx.de>, Anatol Belski <anatol.php@belski.net>, 
	PHP Webmaster ML <php-webmaster@lists.php.net>, =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>, 
	PHP Development <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1142355c083aab051897cfe6
Subject: Re: [PHP-WEBMASTER] Re: [PHP-DEV] PHP7 releases vs Windows Sources?
From: pierre.php@gmail.com (Pierre Joye)

--001a1142355c083aab051897cfe6
Content-Type: text/plain; charset=UTF-8

On Jun 16, 2015 1:34 AM, "Hannes Magnusson" .
> >
>
>
>
> Thats what we want. We want the official release balls to be generated
> by an "official server" using the official toolchain.

For the tarballs? Yes. Only that it does not happen last time I checked.

> There should never be a time when a Release Manager pulls up his
> notebook, does a checkout and packages that and uploads. Its bad
> enough we have this for pecl exts, but there is no reason for php-src
> to be playing with fire and infiltration agencies.

It was the goals of snaps, but given the issues we have to keep it up,
running and accessible, it does not happen.

As of "infiltration agencies", code signing helps. Using https (htts)
helps. But you did not want it.

> That has unfortunately happened before, and resulted in us
> distributing .orig files (patch conflicts), .exp, .out, .php, ...
> (failed tests results) and even wrongly generated artifacts (due to
> wrong bison/re2c versions installed locally).

Yes, we really need a standard box for that (snaps?).

> We don't want that happen again.
> The official releases should be done on "snap box", and be completely
> automated with no room for accidents.
> It produces several archives, and we can add .zip to that mix if not
> already available.
>
> It should be obvious that any binary distribution that aims to be
> official PHP.net release should use this official release, not some
> custom mix of things.
> It is important that these official binaries also don't regenerate the
> files in the archive.
> If there is an extra file (.w32?), or touching of files, required to
> make this archive usable to generate binaries from - then please fix
> the root problem; touch the file before the packaging (and update the
> README :)).

The sources zip archives have no code difference. They are a convenient
archive used by many builds tools. That did not change since the last time
we discussed that.

>
> -Hannes
>
> --
> PHP Webmaster List Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--001a1142355c083aab051897cfe6--