Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67659 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39978 invoked from network); 8 Jun 2013 19:46:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jun 2013 19:46:35 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.67 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.67 smtp67.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.67] ([108.166.43.67:56458] helo=smtp67.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EE/30-38360-A1A83B15 for ; Sat, 08 Jun 2013 15:46:35 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 85D001480B5; Sat, 8 Jun 2013 15:46:31 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp1.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id AE1201480CD; Sat, 8 Jun 2013 15:46:29 -0400 (EDT) Message-ID: <51B38A15.4080602@sugarcrm.com> Date: Sat, 08 Jun 2013 12:46:29 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= CC: Ferenc Kovacs , Pierre Schmitz , PHP Internals References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 5.4.16 and PHP 5.3.26 released! From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Yes, they should be made public. Not doing this is a process issue. Rather absence of process issue - right now we pretty much have no process of handling security bugs. I'm trying to do what makes sense but sometimes things fall through the cracks - like forgetting to check all the bugs for privacy settings... > to HTML, see README.RELEASE_PROCESS for HTML requirements .. even > beter would be generating NEWS from commit messages ... but small > steps help already) NEWS from commits doesn't seem to be feasible, we tried that some time ago but commits are way too noisy and special syntax just makes people confused and they routinely forget to do it right. HTML from NEWS seems to be doable though - right now it's 90% automatic, make sense to get it to 100%. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227