Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:929 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89174 invoked from network); 15 Apr 2003 23:41:41 -0000 Received: from unknown (HELO cs181147.pp.htv.fi) (213.243.181.147) by pb1.pair.com with SMTP; 15 Apr 2003 23:41:41 -0000 Received: from localhost (jani@localhost) by cs181147.pp.htv.fi (8.11.6/8.11.6) with ESMTP id h3FNfhc13949; Wed, 16 Apr 2003 02:41:43 +0300 X-Authentication-Warning: cs181147.pp.htv.fi: jani owned process doing -bs Date: Wed, 16 Apr 2003 02:41:43 +0300 (EEST) Sender: jani@cs181147.pp.htv.fi Reply-To: Jani Taskinen To: Sascha Schumann cc: internals@lists.php.net In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] 4.3.1 release (was Re: Zend commit) From: sniper@iki.fi (Jani Taskinen) On Wed, 16 Apr 2003, Sascha Schumann wrote: > The primary focus WRT security fixes is the PHP 4.3.1 release I guess you meant the 4.3.2 release, since there already is 4.3.1 out there? :) > Looking at TODO_SEGFAULT, we have addressed about 20 issues > with 9 remaining open. It would be good, if those which > affect ext/standard/* would be fixed before the next release. > Others (e.g. in the dbase extension) are not that urgent. > > Any comments regarding the release process? Such as..? I've just been waiting that the issues in TODO_SEGFAULT get fixed before rolling the release package. Speaking of which, we should propably start making the release packages at the snaps.php.net machine to be absolutely sure we always use the same versions of the tools needed for it (autoconf, etc). It would be nice if I got shell access there to be able to do this.. --Jani