Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75819 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21411 invoked from network); 22 Jul 2014 07:01:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jul 2014 07:01:51 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.217.172 mail-lb0-f172.google.com Received: from [209.85.217.172] ([209.85.217.172:36282] helo=mail-lb0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 12/15-14611-C5C0EC35 for ; Tue, 22 Jul 2014 03:01:50 -0400 Received: by mail-lb0-f172.google.com with SMTP id z11so5570253lbi.31 for ; Tue, 22 Jul 2014 00:01:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=vBEbGbCXudEUi3GnqgFu667UhtyPeIoy+89xKOk+AoM=; b=GY6Np2q0GtUjjcFDEcf9N2080lytPAmzbIPA0Wuw6jPIA5vFgNeRFB3y5qsMn/a03X 96VDF2PGMl8cy5yNtY68+hS2D4Wp3l/v/7dILimolxMvDRRRDp0h0/LGwxc89LRMf4Pb m01tNndvqsQ0YivrDRPJo0bjwuSg2kRcTiwLGAEDMwDg0NuRDbrzm0yn3pI/xNq/O+Hp pL3PV0y7pJ5p9eUM//RPvtSptEG/PPfL4F5vcgn0BB7XWCBRaXQMsB7j0zhZArXShaL/ LkRoZjceueIy919pktvSu3i126yj41kkjZPDKdhqronlU4LxQdIaI7UjF20ZB7DY+RqI OHTQ== X-Received: by 10.112.40.161 with SMTP id y1mr30728707lbk.61.1406012505436; Tue, 22 Jul 2014 00:01:45 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.128.202 with HTTP; Tue, 22 Jul 2014 00:01:05 -0700 (PDT) In-Reply-To: <53CDF9CD.4050902@gmx.net> References: <53CDF9CD.4050902@gmx.net> Date: Tue, 22 Jul 2014 16:01:05 +0900 X-Google-Sender-Auth: ouly9uZ4jzWDmj9UjZhT8Pi31ck Message-ID: To: David Soria Parra Cc: David Soria Parra , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11345cc2efb6e904fec2cb5d Subject: Re: [PHP-DEV] RFC: Move phpng to master From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11345cc2efb6e904fec2cb5d Content-Type: text/plain; charset=UTF-8 Hi David, On Tue, Jul 22, 2014 at 2:42 PM, David Soria Parra wrote: > > > > Even if we have PHP-5.7 branch, we have merge up policy. Therefore, > > any new feature will end up with master, I suppose. If a new feature is > > only available to PHP-5.7 branch, it's a merge bug, isn't it? > > > > Regards, > > We had this policy before and it didn't help us. The problem is > maintiaining all the branches and keeping people interested in the next > branch because people tend to focus on the currently release branch. > When we decided upon the release RFC we talked a lot about the overhead > of maintaing multiple branches and tried to reduce the amount of > branches. In particular with API changes it becomes tidious if we try to > maintain a feature across branches and that implicit divergence has to > be resolved better sooner or later, or otherwise it would be just like > the old php6 again. I can understand your concern. We have git now and git can easily spot what and who haven't merged required changes to master. Working with multiple branches and merge is much easier with git also. I think this time it will work, hopefully. My concern is development time. It's too short. We only have about half of a year to feature freeze. More than a year would be appropriate for a major version up, IMHO. Long alpha/beta period is good for users also. Having PHP-5.7 is not a mandatory, but I would like to have it. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11345cc2efb6e904fec2cb5d--