Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 74E6F200C08 for ; Thu, 26 Jan 2017 17:01:32 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 73891160B4C; Thu, 26 Jan 2017 16:01:32 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BEB0B160B40 for ; Thu, 26 Jan 2017 17:01:31 +0100 (CET) Received: (qmail 22720 invoked by uid 500); 26 Jan 2017 16:01:30 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 22708 invoked by uid 99); 26 Jan 2017 16:01:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jan 2017 16:01:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 640B21A082F for ; Thu, 26 Jan 2017 16:01:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id e3zrBV8Mk5MJ for ; Thu, 26 Jan 2017 16:01:26 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0DD1B5FE3E for ; Thu, 26 Jan 2017 16:01:26 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 28F56E043B for ; Thu, 26 Jan 2017 16:01:25 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 83C0725290 for ; Thu, 26 Jan 2017 16:01:24 +0000 (UTC) Date: Thu, 26 Jan 2017 16:01:24 +0000 (UTC) From: "Michael Wall (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (ACCUMULO-4480) User manual test results section MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 26 Jan 2017 16:01:32 -0000 [ https://issues.apache.org/jira/browse/ACCUMULO-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wall reassigned ACCUMULO-4480: -------------------------------------- Assignee: Michael Wall > User manual test results section > -------------------------------- > > Key: ACCUMULO-4480 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4480 > Project: Accumulo > Issue Type: Task > Components: docs > Affects Versions: 1.8.0 > Reporter: Christopher Tubbs > Assignee: Michael Wall > Fix For: 1.8.1, 2.0.0 > > > I noticed today that the user manual administration chapter (administration.txt) contains information about specific older releases, which is stale. > In particular, it contains assertions about the stability of specific combinations of Accumulo, Hadoop, and ZooKeeper versions, for older Accumulo releases, based on testing. This information is not appropriate for the user manual, and would be better presented in the release notes for particular releases. The user manual should be written agnostic to the current version, whenever possible. > Additionally, the client configuration section contains information about version 1.6.0, in the present tense. Change in behavior at a version boundary should be written in such a way as to convey that a the behavior changed (past tense) across that boundary, rather than be written to correspond to the current release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)