Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:59228 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61193 invoked from network); 30 Mar 2012 09:44:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Mar 2012 09:44:22 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.213.42 mail-yw0-f42.google.com Received: from [209.85.213.42] ([209.85.213.42:43953] helo=mail-yw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0D/71-53104-470857F4 for ; Fri, 30 Mar 2012 04:44:21 -0500 Received: by yhfq11 with SMTP id q11so191011yhf.29 for ; Fri, 30 Mar 2012 02:44:18 -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 :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=8UtsBIIC/oRX3IVwZQQlYa7y5E8aLJEBy6vbn305wto=; b=LUx1MvPhuf2TYV0a1FzLNyoCuhIVMmQEEE29aHKI96sAL29fUeeeTk8yRBtA0L+4Os UGKZ4ZQc9VD8WY5lrfPz18gD2PQSasphnCVTx/kA6hsi8nAFqelAqHr7XXsiSrx5KVvE 90hBSZ8RPLNuwX14WwYuKH9TkuMeriFhEHNDnwE83KjuVcNdA1ya3I6lgUslGMWno0pV dn80guRWEFPQHJGiBL7P5PFgGCS0bSpIKqFoebFTb2JzCZ5uV0TlfSJAkmvjHwRgzu6U jjFTgTp6tfCoXpANa3cgo58xYy9ETt+BEVZabPuTK4e1AO817QYTc558S3gjm9/iJM9Q 2bfA== Received: by 10.236.191.169 with SMTP id g29mr1236372yhn.103.1333100658245; Fri, 30 Mar 2012 02:44:18 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.146.86.14 with HTTP; Fri, 30 Mar 2012 02:43:38 -0700 (PDT) In-Reply-To: References: Date: Fri, 30 Mar 2012 18:43:38 +0900 X-Google-Sender-Auth: EiiMB2FgMyiq9npXmArWFymy4Wg Message-ID: To: Pierre Joye Cc: internals@lists.php.net, Stas Malyshev , ohannes@php.net Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] Merge from 5.3 and/or 5.4. What's the current policy? From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi 2012/3/30 Pierre Joye : > hi, > > On Fri, Mar 30, 2012 at 10:22 AM, Yasuo Ohgaki wrote: > >> Bug fix can be merged upwards. However, >> Are we free to merge feature changes? > > > Generally speaking, no. I thought so. > >> Adding new module constant is new feature. > > Not necessary, for example in Curl or openssl, many constants addition > do not change the implementation per se. But it has to be discussed > from a case by case basis. > >> Before git, we just commit new feature/changes >> to trunk and we could think/argue about merge >> later. Now we need to think/argue about merge, >> then commit. > > Right, and that's actually very good. The commit first then try to > discuss is finally over. For large changes, discussing first is good. For small changes like this, it may be too much. > >> We need some guidelines for feature changes, >> if we are going to keep "merge upward" policy. > >> Anyway, RM of 5.3/5.4 are okay to add module >> constants to pgsql? If there is no objection, I'll >> commit the change and updates docs. > > RMs apply the developers decisions, in general. So please post your > proposals to the list, CCing them :) https://gist.github.com/2250214 The change is simple one. Just making constants available defined in pg-config.h The only reason why I've made this thread for this simple change is "merge upward" policy. Someone suggested gitflow, the flow would be better for faster development. -- Yasuo Ohgaki yohgaki@ohgaki.net