From dev-return-2722-apmail-bloodhound-dev-archive=bloodhound.apache.org@bloodhound.apache.org Mon May 13 17:59:58 2013 Return-Path: X-Original-To: apmail-bloodhound-dev-archive@www.apache.org Delivered-To: apmail-bloodhound-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EE1801120D for ; Mon, 13 May 2013 17:59:57 +0000 (UTC) Received: (qmail 40679 invoked by uid 500); 13 May 2013 17:59:57 -0000 Delivered-To: apmail-bloodhound-dev-archive@bloodhound.apache.org Received: (qmail 40661 invoked by uid 500); 13 May 2013 17:59:57 -0000 Mailing-List: contact dev-help@bloodhound.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@bloodhound.apache.org Delivered-To: mailing list dev@bloodhound.apache.org Received: (qmail 40645 invoked by uid 99); 13 May 2013 17:59:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 17:59:57 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [209.85.128.51] (HELO mail-qe0-f51.google.com) (209.85.128.51) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 17:59:52 +0000 Received: by mail-qe0-f51.google.com with SMTP id x7so3739319qeu.24 for ; Mon, 13 May 2013 10:59:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=+gxc8/DgZG+pye+iNqNvZLC+Lgdls9RA8tPuKZe0XiE=; b=fWylljIp3JMgAeTdEvUNh+n1aqi+eY7lCKyfeFy5XOtg1vDTzByu4MqM/cQ96ziJYk 2zJnP94X4dfkNbnm8J2ysTaTdvYK7Ctbgk9mW3F6mwBJY1jzK8sLTFVzeSKSc8tiXE/G UI+p79KCjOsU3jShEgJP27TYwiNNx/AlX3sW+ep5Bgz+Di+cN4se/cdE4oRiI4nTF7dX ydwltMZwoTnR0Hk/vk73Hd7YQtsR4GVt/oueQNY7RwZBJNEe9Lbf+Zu+JoCiSQWHPfhh nOfmO+zrbgE4TcKXQYtJxZV2Tt7GfaNm0OUhtcdVxRFqTu6mYBdtY9kQdu3G5HtCM0vr AyNA== MIME-Version: 1.0 X-Received: by 10.229.165.144 with SMTP id i16mr340925qcy.156.1368467950903; Mon, 13 May 2013 10:59:10 -0700 (PDT) Received: by 10.49.109.167 with HTTP; Mon, 13 May 2013 10:59:10 -0700 (PDT) In-Reply-To: References: <058.07c076831267021bcbee7f776cb82f36@bloodhound.apache.org> <073.4a231259a2a387ea89fdc8b993fbbd71@bloodhound.apache.org> Date: Mon, 13 May 2013 19:59:10 +0200 Message-ID: Subject: Re: [Apache Bloodhound] #521: Relations error on ticket page From: Andrej Golcov To: dev@bloodhound.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQm1/0PhsC6O+1m+ehYigGt/jKWOD35WrVdk0nMKKC44A4Vmn4VepedMoUqvZl3RlLZun9An X-Virus-Checked: Checked by ClamAV on apache.org > Relations are a component of Bloodhound, and a "relations" component is > already set up, so I would suggest that's the best way to distinguish > relations tickets. You can of course use keywords in addition to that. I was not sure that "relations" directly refers BEP-6 implementation. Otherwise, agree: there is no need for double reference in component and keywords. Changed this appropriately. Cheers, Andrej