Newsgroups: php.internals,php.webmaster
Path: news.php.net
Xref: news.php.net php.internals:86694 php.webmaster:21365
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.169 as permitted sender)
Message-ID: <557F6054.4000308@gmail.com>
Date: Mon, 15 Jun 2015 16:31:32 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Hannes Magnusson <hannes.magnusson@gmail.com>
CC: Anatol Belski <anatol.php@belski.net>, =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8?=
 =?UTF-8?B?dGVy?= <johannes@schlueters.de>, 
 Christoph Becker <cmbecker69@gmx.de>,
 PHP Development <internals@lists.php.net>, 
 PHP Webmaster ML <php-webmaster@lists.php.net>
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> <CADNQb0XjnfdSpVj5zqtjZ6z4bMsZfxuXOOAE+ok8jp1HQFY_SA@mail.gmail.com>
In-Reply-To: <CADNQb0XjnfdSpVj5zqtjZ6z4bMsZfxuXOOAE+ok8jp1HQFY_SA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] PHP7 releases vs Windows Sources?
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> gpg-agent forwarding over ssh?

Well, if that works then fine. I never tried it (actually didn't use the
agent that much at all) but why not.

> - 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"

Looks good so far, except that I'd probably feel better doing the tag
manually. First because it can be moved around (forgot to update news,
last minute patch, made typo somewhere, added CVE, etc.), second again
because it's signed and I kind of feel more confident knowing I (or
other RM) is the guy who actually personally created that tag. It's not
a very important point, just a preference, at least for me. If other RMs
feel different then fine with it as is.

> 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

We need to sign the packages, not only tags. Creating tag is actually
not that big a deal manually, it's one git command. Packaging from it is
more involved. But if the agent works, yes, we can do it with scripts,
that's fine.

> 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

I'm all for it. I know my RMship for 5.4 is will be done soon, so my
personal profit from it would be pretty low, but for the sake of next
RMs automating the dozen of manual tasks one has to do to roll the
release would be a nice thing. We just need to be careful with phpweb,
etc. patching given that we can have 3 branches being released in
parallel, sometime conflicts happen.

-- 
Stas Malyshev
smalyshev@gmail.com