Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (nike.apache.org: domain of busbey@cloudera.com designates
 209.85.216.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGHyZ6+yXvGCs+_517i+Dt=GZJtbatG+YF-r3VWyW1s3a+8OfQ@mail.gmail.com>
References: <53052278.8050402@gmail.com>
 <CADxc9B=jnnUyPeUL+APhYh5DQ6tqC=HdjF+quC92M-RfzxfSPg@mail.gmail.com>
 <CAL5zq9YQF252KDBU2n==yD9v-OJQyF8dyoyjPhqpwxTRFQor+g@mail.gmail.com>
 <CAGHyZ6LsSqS8N_ag=cQpqHzVMA6SFZ+a28a=xa8xm1iJQTs=yQ@mail.gmail.com>
 <5305A177.6050604@gmail.com>
 <CAGHyZ6+yXvGCs+_517i+Dt=GZJtbatG+YF-r3VWyW1s3a+8OfQ@mail.gmail.com>
From: Sean Busbey <busbey+lists@cloudera.com>
Date: Thu, 20 Feb 2014 01:36:01 -0600
Message-ID: 
 <CAGHyZ6LUPFRDikCS_6BcM2dyfsnjDYuyMg9mhYuW3CFUV-fTug@mail.gmail.com>
Subject: Re: [DISCUSS] CHANGES Documents
To: "dev@accumulo apache. org" <dev@accumulo.apache.org>
Content-Type: multipart/alternative; boundary=001a11c1318ad04de604f2d18f10

--001a11c1318ad04de604f2d18f10
Content-Type: text/plain; charset=UTF-8

On Thu, Feb 20, 2014 at 1:20 AM, Sean Busbey <busbey+lists@cloudera.com>wrote:

>
> On Thu, Feb 20, 2014 at 12:32 AM, Josh Elser <josh.elser@gmail.com> wrote:
>
>>
>>
>>> The more I reread this thread, the more I like the release notes
>>> described
>>> by Eric[2].
>>>
>>
>> While I agree that would be nice, I don't know of a quantitative way to
>> determine that. Is "critical" categorized by some Jira priority? Do we end
>> up omitting something that someone wanted? I feel like we should just
>> bundle all changes for that release or none at that point.
>>
>>
> We're the Accumulo community, we should be cognizant of what changes are
> most likely to impact downstream users. After all, isn't that part of how
> we define a public API in the first place?
>
>
As an illustrative example, consider ACCUMULO-1572. Losing all the roles
attached to a ZK server when it goes down is going to burn any production
deployment of sufficient age. Users will fall into two camps: those already
implementing a workaround (e.g. a watchdog that restarts Accumulo
processes) and those who have gotten lucky.

The latter will most definitely want to hear about this fix in consumable
release notes. Depending on the overhead caused to those in the first camp,
they likely will also be interested. Even if we just started by filtering
based on priority, picking this issue out of the 22 BLOCKER/CRITICAL is
much more reasonable then out of the full list of 144 Closed/Resolved Bug
issues included for 1.5.1.

--001a11c1318ad04de604f2d18f10--