Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93920 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50074 invoked from network); 12 Jun 2016 21:04:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Jun 2016 21:04:20 -0000 Authentication-Results: pb1.pair.com smtp.mail=danack@basereality.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=danack@basereality.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.213.42 cause and error) X-PHP-List-Original-Sender: danack@basereality.com X-Host-Fingerprint: 209.85.213.42 mail-vk0-f42.google.com Received: from [209.85.213.42] ([209.85.213.42:32875] helo=mail-vk0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AD/C4-12403-15ECD575 for ; Sun, 12 Jun 2016 17:04:18 -0400 Received: by mail-vk0-f42.google.com with SMTP id d185so32746509vkg.0 for ; Sun, 12 Jun 2016 14:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dcDYYh+SABYU9UdblYhDB+jyUqTn7qDejZ9ZxPCWS1M=; b=gWAAdBGe8Px5iGxx4tcgZ+lN+GWB4vYAtFyOnBmc8g/K4NZQer65bVN380c1hpajc4 ZveC0/qUz/g+zC4eEBqfrI6KIuixz9r465STflHDbFmYmBPNpE1jOIxQD7L/geRU+FcS l0s3TtNhwLiANLIDUL9dU4mt1MmCJ26k2U/9i4/lHqirNhpqT0EG2e6fiwoQlI+YERFG FHLi37NDBhMHiRJFQwquYJNTWBS6DdWLnM6umDCvgRQOXYbQEkb2L8qtdrpCd5aszuVN DmvHC/F2cy80ERqNS+A3HM5nUwUJF7NL2PM0tgP8Ryc+omkSLMv5NvtUe7PF1i9YBjwd nufQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dcDYYh+SABYU9UdblYhDB+jyUqTn7qDejZ9ZxPCWS1M=; b=K/dgDxrJcUUpHCeutodcOPQOTY0Njl3zDAX46v7DyKadpBmDA8WeeVYppRlVWhysHD cRFvpQbNL1a+E4LhKmZG3383uOaZOkzme4CgWTpJdASiChixV+7wG/6kE1M3d/htx9dL 766rqsCgIq6nHhp/HL7YA/WEeOt3g9QBBcaj5UfdjC0PDuGnChKO/EwuKhf/etJQzJ5Z KLnPaXmFtxQ7Fp6Ef75e5xqaU2FJJAKcfk/WDotuguRPW/T683D8xBLHpQ+jrfaFQ650 2gJcDPwXBDdnzQx6cRFFD5WI0ewHUf5XHQ8PGILkQfWSD8ie2Z89159yl8Hi9w+Jz4JM jQ0w== X-Gm-Message-State: ALyK8tK/a6Is4+ZsLeOZed+UzskOkGBRzALDHBTYkWMlyoQm3DSGVPfiPIDgIAOXfJ/aeo9tRG9dV+YY3FJgAw== X-Received: by 10.31.13.70 with SMTP id 67mr4991870vkn.9.1465765455320; Sun, 12 Jun 2016 14:04:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.38.52 with HTTP; Sun, 12 Jun 2016 14:04:14 -0700 (PDT) X-Originating-IP: [2.99.232.113] In-Reply-To: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com> References: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com> Date: Sun, 12 Jun 2016 22:04:14 +0100 Message-ID: To: Rowan Collins Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable? From: danack@basereality.com (Dan Ackroyd) On 12 June 2016 at 17:42, Rowan Collins wrote: > - We have an RFC [too_few_args] about to pass that seems to break our > published Release Process. The "Release Process" is an RFC: https://wiki.php.net/rfc/releaseprocess There are no rules against a new RFC changing the decision from a previous RFC. If you want to have rules that either limit what RFCs can be made, or when certain RFCs can be introduced, then you almost certainly need to introduce the concept of a 'constitution' or other set of rules that exist above the RFC process. If there is a BC break in an RFC, you are free to point this out as a reason to vote against the RFC. cheers Dan Ack