Re: PHP 8.2 Release Manager Selection
| From: | Christoph M. Becker | Date: | Tue, 26 Apr 2022 10:57:05 +0000 |
| Subject: | Re: PHP 8.2 Release Manager Selection | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-117612@lists.php.net to get a copy of this message | ||
On 26.04.2022 at 12:31, Mark Randall wrote:
> On 25/04/2022 12:51, Christoph M. Becker wrote:
>
>> Please put your name forward here if you wish to be considered a
>> candidate. An initial TODO page has been added to the wiki and contains
>> provisional dates for GA and pre-releases[2].
>
> I could potentially be interested in helping out with this, but I do
> have a question about it, mainly, why hasn't most of this been automated
> at this point?
>
> I was reading through the release process notes and am not seeing any
> obvious blocks on most of it that could not be accomplished via a
> suitable CI/CD pipeline.
>
> Is it just a matter of someone having time available to do it?
>
> The one thing which does make me ponder is would we need to assign a GPG
> key to the build process?
>
> I'd be happy to give some of my time later this year to further
> investigate this.
There are docker images available[1] which automate parts of the build
process. However, doing the builds is only a rather small part of the
obligations of a release manager, and the other tasks (such as deciding
whether to merge a pull request, doing bug triage, and deciding on the
actual release schedule) cannot be automated.
[1] <https://github.com/sgolemon/php-release>
--
Christoph M. Becker