Newsgroups: php.internals,php.webmaster
Path: news.php.net
Xref: news.php.net php.internals:86693 php.webmaster:21364
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <557F55CF.1060602@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>
	<018b01d0a7a4$b572f730$2058e590$@belski.net>
	<CADNQb0WkXH-M0Yc5gD6+-=x4YEzMD0eNNwuo3u1=ghpz5i=ENw@mail.gmail.com>
	<557F55CF.1060602@gmail.com>
Date: Mon, 15 Jun 2015 16:13:18 -0700
Message-ID: <CADNQb0XjnfdSpVj5zqtjZ6z4bMsZfxuXOOAE+ok8jp1HQFY_SA@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Anatol Belski <anatol.php@belski.net>, =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>, 
	Christoph Becker <cmbecker69@gmx.de>, PHP Development <internals@lists.php.net>, 
	PHP Webmaster ML <php-webmaster@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] PHP7 releases vs Windows Sources?
From: hannes.magnusson@gmail.com (Hannes Magnusson)

On Mon, Jun 15, 2015 at 3:46 PM, Stanislav Malyshev <smalyshev@gmail.com> wrote:
> Hi!
>
>>> It's a worthy goal IMHO. Currently it all is done manually as you know.
>>
>>
>> What! No, I didn't know.
>> I was describing how the process used to be, and I thought it still was.
>
> I think making auto-release is a nice idea, but what about signing? I'm
> surely not leaving my personal private key on any commonly accessible
> server, so how would I sign packages? Except for that, making script
> that would do "make release" or "sh scripts/release" and complete the
> release cycle (including generating & uploading everything) would be
> nice. Right now we have mkdist but it only takes us half-way.


gpg-agent forwarding over ssh?



- Goto https://release.php.net/
- Login with your master credentials (only allows logins for whitelisted users).
- White page suggest you are creating x.y.z+1 release from branch x_y
- If yes; press "MAKE MAGIC"
- If no; write the version number in input field, select branch from combobox
- Press; "I KNOW WHAT IM DOING"

This will trigger generating all files needed, bumping version and
whatever. Tags. Creates archives. All that good stuff.
"5 minutes later" you get email; "release is ready!" with links to the archives

You fetch them, explore the archives, run the tests and you the things
we all know we should do but don't :)
Then:

ssh -R ~username/.gnupg/S.gpg-agent -o "StreamLocalBindUnlink=yes"
release.php.net '/usr/local/bin/confirm x.y.z+1'

It'll sign the git tag (using your forwarded agent), push upstream,
push archives to php-distribution.git

Then. In the next release of the tool:
- The whitepage extracts the NEWS entries and does the html/php
formatting for phpweb
- Gives you checkboxes to choose pick the highlights
- The highlights will be used for the standard phpweb news xml.
....
- Profit


-Hannes