Return-Path: Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: (qmail 89574 invoked from network); 25 Feb 2011 22:54:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Feb 2011 22:54:17 -0000 Received: (qmail 80562 invoked by uid 500); 25 Feb 2011 22:54:17 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 80514 invoked by uid 500); 25 Feb 2011 22:54:16 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 80506 invoked by uid 99); 25 Feb 2011 22:54:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Feb 2011 22:54:16 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of todd@cloudera.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-iw0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Feb 2011 22:54:07 +0000 Received: by iwr19 with SMTP id 19so1958623iwr.35 for ; Fri, 25 Feb 2011 14:53:46 -0800 (PST) Received: by 10.42.140.72 with SMTP id j8mr1411991icu.64.1298674426341; Fri, 25 Feb 2011 14:53:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.42.201 with HTTP; Fri, 25 Feb 2011 14:53:26 -0800 (PST) From: Todd Lipcon Date: Fri, 25 Feb 2011 14:53:26 -0800 Message-ID: Subject: Request: federation JIRA naming? To: hdfs-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=90e6ba6e8be8dc67e4049d23332b X-Virus-Checked: Checked by ClamAV on apache.org --90e6ba6e8be8dc67e4049d23332b Content-Type: text/plain; charset=ISO-8859-1 Hey folks, Would those of you working on a branch mind adopting a naming convention for all the federation tickets? I'm really glad to see all the changes going upstream but it's getting confusing to separate out what are bugs that apply to trunk vs bugs that are just due to the federation branch being in flux. Perhaps a "Federation: " prefix for all the JIRA titles? I'm happy to go through and edit the ones that are already up. If I'm the only one that finds these confusing, feel free to tell me to shove off and just deal with it :) -Todd -- Todd Lipcon Software Engineer, Cloudera --90e6ba6e8be8dc67e4049d23332b--