True, but at the same time it makes no sense to release 1.6.0 if the
features contained within are incomplete.
There are still a number of blockers that are unresolved that would all
fall into the category of creating a broken 1.6.0 or having to back out
large changesets. I know these blockers would be categorized as "bug
fixes" and not "features", but some of these bugs are directly from new
features which I would argue are thus still a part of this feature.
I'm all for trying to release early and often, but I will be the guy who
throws a wrench in the works if we do it at the sake of reducing the
quality of our release.
On 10/25/13 11:49 AM, John Vines wrote:
I'd rather not go down the slippery slope we went down last time. I'll
gladly be the bad guy and say that things are getting pushed to 1.7.
On Fri, Oct 25, 2013 at 2:23 PM, Christopher <[email protected]> wrote:
It looks like we're 50% in terms of tickets complete.
http://s.apache.org/accumulo-1.6.0-issues
Extensions are always nice, but I'm not going to be the bad guy and
ask for one :)
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Fri, Oct 25, 2013 at 12:33 PM, John Vines <[email protected]> wrote:
Alright folks, we're down to the wire. Feature freeze is one week away.
If
anyone has any last minute concerns about this schedule, please speak up
now. Otherwise, have a great weekend!
