Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63044 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41179 invoked from network); 17 Sep 2012 22:00:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Sep 2012 22:00:47 -0000 X-Host-Fingerprint: 217.114.211.68 unknown Date: Mon, 17 Sep 2012 18:00:47 -0400 Received: from [217.114.211.68] ([217.114.211.68:28893] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C0/AC-07072-E8D97505 for ; Mon, 17 Sep 2012 18:00:47 -0400 To: internals@lists.php.net References: <1347893073.5709.2986.camel@guyrush> <50574593.7020009@php.net> User-Agent: slrn/0.9.9p1 (SunOS) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: X-Posted-By: 217.114.211.68 Subject: Re: [PHP-DEV] Moving forward: PHP 5.5 From: dsp@php.net (David Soria Parra) On 2012-09-17, 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? Yes, merging NEWS, writing news entries, mails and generating Changelog-5 (the issue is related to NEWS). Most of the rest can be automated so once a release hit .0 it's, as johannes pointed out, very straight forward