Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DBFDA613D for ; Fri, 20 May 2011 16:18:14 +0000 (UTC) Received: (qmail 94795 invoked by uid 500); 20 May 2011 16:18:13 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 94679 invoked by uid 500); 20 May 2011 16:18:12 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 94671 invoked by uid 99); 20 May 2011 16:18:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 May 2011 16:18:12 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of daniel.doubleday@gmx.net designates 213.165.64.22 as permitted sender) Received: from [213.165.64.22] (HELO mailout-de.gmx.net) (213.165.64.22) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 20 May 2011 16:18:05 +0000 Received: (qmail invoked by alias); 20 May 2011 16:17:43 -0000 Received: from p578bde86.dip0.t-ipconnect.de (EHLO caladan.smeet.de) [87.139.222.134] by mail.gmx.net (mp036) with SMTP; 20 May 2011 18:17:43 +0200 X-Authenticated: #3445653 X-Provags-ID: V01U2FsdGVkX1+Ss7IqcouSG1Bad6UwySSZKPwbgOmDDQM52DEnu1 jsywBGOfQVXvne From: Daniel Doubleday Content-Type: multipart/alternative; boundary=Apple-Mail-3--963935440 Subject: Documentation of Known Issues Date: Fri, 20 May 2011 18:17:42 +0200 Message-Id: <172F3129-5464-4CF3-8FA6-17E5845274DC@gmx.net> To: user@cassandra.apache.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-Y-GMX-Trusted: 0 --Apple-Mail-3--963935440 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi all I was wondering if there might be some way to better communicate known = issues.=20 We do try to track jira issues but at times some slip through or we miss = implications. Things like the broken repair of specific CFs. = (https://issues.apache.org/jira/browse/CASSANDRA-2670). I know that this = potentially dups jira but maybe tasks could get tagged and some magic = filter could show a list. Or something like a simple wiki page that = lists the known issues that might not be critical such as the mentioned = bug but still are a pain if it happens to you. Cheers, Daniel --Apple-Mail-3--963935440 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Hi all

I was wondering if there might be some way to better communicate known issues.

We do try to track jira issues but at times some slip through or we miss implications.

Things like the broken repair of specific CFs. (https://issues.apache.org/jira/browse/CASSANDRA-2670). I know that this potentially dups jira but maybe tasks could get tagged and some magic filter could show a list. Or something like a simple wiki page that lists the known issues that might not be critical such as the mentioned bug but still are a pain if it happens to you.

Cheers,

Daniel

--Apple-Mail-3--963935440--