Newsgroups: php.internals,php.webmaster
Path: news.php.net
Xref: news.php.net php.internals:86720 php.webmaster:21384
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
Message-ID: <1434475078.21120.12.camel@kuechenschabe>
To: Pierre Joye <pierre.php@gmail.com>
Cc: Anatol Belski <anatol.php@belski.net>, Christoph Becker
 <cmbecker69@gmx.de>,  Hannes Magnusson <hannes.magnusson@gmail.com>, PHP
 Webmaster ML <php-webmaster@lists.php.net>, PHP Development
 <internals@lists.php.net>
Date: Tue, 16 Jun 2015 19:17:58 +0200
In-Reply-To: <CAEZPtU5QtuXoF=eO5BbXxWB32ec3ioLKzJbs53acSVZTG1BL4A@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>
	 <CAEZPtU5QtuXoF=eO5BbXxWB32ec3ioLKzJbs53acSVZTG1BL4A@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
	boundary="=-ujdcZ6qO5wxO/5cMsd8p"
Mime-Version: 1.0
Subject: Re: [PHP-DEV] Re: [PHP-WEBMASTER] RE: [PHP-DEV] PHP7 releases vs
 Windows Sources?
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

--=-ujdcZ6qO5wxO/5cMsd8p
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 2015-06-15 at 22:45 +0700, Pierre Joye wrote:
> Yep, this could work and were probably proper solution. Except we
> wouldn't add some issue for the non Windows users :) I'm not sure, why
> is it done so ATM, probably it has its historical reasons. But this
> would probably cause us need to update the release process procedure?
> And, for PHP7 or for any other as well? Currently that zipball is just
> generated with the build process, so it'll need to be sent over
> somehow. Were anyway doable,  wondering what the other RMs would say.
> Frankly, I'd leave it as it is - as long as it's reachable and
> documented.
>=20
> The reason is that we generate zip for binaries, and we just do the
> same for the src, providing zip archives using the same naming
> convention.
>=20
> We know many other tools relying on these zip, normalized URLs, so we
> must keep them. It does not hurt anyone anyway.

As I said in early 5.3 times already: I'd love if we'd find a process
and layout to have a single source for all downloads and distribute all
downloads from our mirror network, not having Windows as second class
citizen somewhere else but via all ~70 mirrors.

Yes this would hurt short term as we'd have to change some processes and
yes it might change URLs (which can be solved via proper redirects) but
long term users get faster downloads and a single place to go with no
confusion like the one that started this thread.

johannes


--=-ujdcZ6qO5wxO/5cMsd8p
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAABAgAGBQJVgFpHAAoJEH3sTmn8nIPXlwwH/0WrrATU2sO9MYA15y2eNF3U
o4zf6bJWVZdCQ7uHeJh694Iid9UaSh/zJ2VQB4MWvB1qNC9oH/7rI9zV4/QH6Uz2
V8RxDJ5AHj37bDW/SjteChleQ/VoA6y9EkFKwmgCGkJ8yHdrZkw1csEuF26LM15G
gSzMJ6v4HEJ093TJHUnS221JESlYJN2tyqIRgIZJM8aUmU6Z/egJXzchjSZBHevF
u3cXXAGH2gEGzZaE+bBBWd7/qaR3Y8oj8/fomrxR4swbOi+ET2OZj92S1uzmVU/5
bUQ8rVv0SXoKHIqFs7zRAYXcGFQF2cblt5xH8/cc/U6YKskybcPbfe9v+6taneo=
=gvFM
-----END PGP SIGNATURE-----

--=-ujdcZ6qO5wxO/5cMsd8p--