Mailing-List: contact dev-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
MIME-Version: 1.0
In-Reply-To: <CAFh+7k16zEg_WFVeSO5EZ4tiptWCBFONEe1Y4p2EgQ5kznMRcg@mail.gmail.com>
References: <CAFh+7k16zEg_WFVeSO5EZ4tiptWCBFONEe1Y4p2EgQ5kznMRcg@mail.gmail.com>
From: Kirk Lund <klund@apache.org>
Date: Thu, 1 Jun 2017 14:45:51 -0700
Message-ID: <CAJrNg01tG=x8VhxLq54RPYCVmfy_USpu38xPUnqykc1BjzoJZA@mail.gmail.com>
Subject: Re: [DISCUSS] Discussions of API changes missing or lost in noise
To: geode <dev@geode.apache.org>
Content-Type: multipart/alternative; boundary="94eb2c058cf4ea8ef40550ecf554"
archived-at: Thu, 01 Jun 2017 21:45:54 -0000

--94eb2c058cf4ea8ef40550ecf554
Content-Type: text/plain; charset="UTF-8"

+1 to initiating a [DISCUSS] thread on dev list for any proposed changes to
the public API(s).

On Thu, Jun 1, 2017 at 2:09 PM, Dan Smith <dsmith@pivotal.io> wrote:

> Hi devs,
>
> This is similar to the discussion John started about keeping track of
> changes to geode. I'm seeing some changes happening to the public API that
> I feel like maybe should have a more visible discussion. For example
> GEODE-2892 (Region.sizeOnServer) or GEODE-3005 (new API for partitioning).
>
> I think we should have a clear policy to send an email with [DISCUSS] in
> the header to mailing list for changes to the public API, behavior, or
> dependencies. Or wiki
> <https://cwiki.apache.org/confluence/display/GEODE/
> Criteria+for+Code+Submissions>
> says that changes should be discussed, but it doesn't really specify how.
>
> Part of the issue is that I find it impossible to keep up with the amount
> of JIRA noise on the dev list, so just creating a JIRA is not enough for me
> to notice a new API change. I propose that we segregate all of this
> automated email onto a separate list, either geode-commits or some new
> list. I'd like to segregate anything not directly sent by a human - JIRAs,
> PRs, and reviewboards.
>
> -Dan
>

--94eb2c058cf4ea8ef40550ecf554--