Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63043
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Sebastian Bergmann <sebastian@php.net>
Cc: internals@lists.php.net
In-Reply-To: <50574593.7020009@php.net>
References: <slrnk4mc5m.g88.dsp@experimentalworks.net>
	 <1347893073.5709.2986.camel@guyrush>
	 <CAAUB37AMvDgiwZRyTfECocPxLJzU5e46svEmuB6mWqeohCfhag@mail.gmail.com>
	 <CAMUwpuRH155NHYr_ATU4ShJyk9PGc0K1dCa+VsF=qTtPAXf=Og@mail.gmail.com>
	 <1347896176.5709.3002.camel@guyrush>  <50574593.7020009@php.net>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 17 Sep 2012 21:00:04 +0200
Message-ID: <1347908404.5709.3017.camel@guyrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Moving forward: PHP 5.5
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Mon, 2012-09-17 at 17:45 +0200, Sebastian Bergmann wrote:
> Am 17.09.2012 17:36, schrieb Johannes Schlüter:
> > There are very few special processes. In fact the only RM-specific
> > things are around packaging the tarballs up, while that's described in
> > an README.
> 
>  Does this have to be manual process? Is there something in it that
>  cannot be described in a Makefile, build.xml, etc. instead?

Even that would have to be triggered ;-)

And well, then there are tasks which can't be automated, like writing a
release announcement (human has to decide what's to be highlighted etc.)
but well, there automation there is the less we need two guys doing
that, the more you're confirming my point.

johannes