Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50415 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99646 invoked from network); 23 Nov 2010 01:21:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Nov 2010 01:21:39 -0000 Authentication-Results: pb1.pair.com smtp.mail=felipensp@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=felipensp@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: felipensp@gmail.com X-Host-Fingerprint: 209.85.161.42 mail-fx0-f42.google.com Received: from [209.85.161.42] ([209.85.161.42:50105] helo=mail-fx0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F5/C6-59959-1271BEC4 for ; Mon, 22 Nov 2010 20:21:38 -0500 Received: by fxm11 with SMTP id 11so225020fxm.29 for ; Mon, 22 Nov 2010 17:21:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=OmPyqnMQKaHQxKuzX+0h32XIWqRrOV2l4CuCdQ0S+n4=; b=eoiSKq6zEuYfq8COtpJK4FxDGCsho7Q6kC51WAGqX0S4zKDEUHlLTeso23JJxr07qd OBVxG5GlXLz3XxVirDgqW/s0eDK8RQC2PZcQYR8ZBhLUkusmlQjLVvo+N8lskxKqLu7u 0yblwKjGp0uL6ItsZYosOFcP4xoWSGqPeJQz8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=Uin4H4b4+mszsl2SYMBhgpa5D37OtkdTbukiLUOtFZ2TmKNVy5jrfvVaPLHB8DIRQ6 Pc2OPAK2iLLN78XgvnOEO2iNGRJ3GxB3VMxhpq8dSHmrr+/om/vniGT06hW2xgZtiEi0 x6FTuLSnHV27XQH30QxJ2fUslt86KFDAInDKA= Received: by 10.223.116.1 with SMTP id k1mr4844964faq.51.1290475294184; Mon, 22 Nov 2010 17:21:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.52.146 with HTTP; Mon, 22 Nov 2010 17:21:13 -0800 (PST) Date: Mon, 22 Nov 2010 23:21:13 -0200 Message-ID: To: internals Content-Type: multipart/alternative; boundary=001636eef06580573f0495ae312f Subject: [RFC] Release Process From: felipensp@gmail.com (Felipe Pena) --001636eef06580573f0495ae312f Content-Type: text/plain; charset=UTF-8 Hi, With the recent chaos in the way we begin and ended releases, we would like to propose a clean way to deal with releases and related decisions: [1] PHP releases have always been done spontaneously, in a somehow chaotic way. Individual(s) decided when a release will happen and what could or could fit in. Release managers role are unclear and the way to nominate them is not clearly defined either. The goals of this RFC aim to solve these issues while giving to us, our users and 3rd parties (distributions, contributors, etc.) more visibility and the ability to actually have a roadmap, or plan developments. This RFC aims to define: * a clear release cycle, periodic * a transparent decision process for the feature additions, via the RFCs and a transparent but anonymous vote * which changes can be done during a release lifetime (BC breaks, bugs fixes, security fixes, etc.) * a transparent way to choose release managers for a given release * a better usage of bugs.php.net to track each change, addition, bug fixes (security incl.) or other various tasks related to a release * reduce time between bugs fix releases * reduce the time to get new features in a release * suppress BC breaks in bugs fix releases * feature(s) preview release [1] http://wiki.php.net/rfc/releaseprocess -- Regards, Felipe Pena --001636eef06580573f0495ae312f--