From hdfs-dev-return-2316-apmail-hadoop-hdfs-dev-archive=hadoop.apache.org@hadoop.apache.org Sat Feb 26 06:39:33 2011 Return-Path: Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: (qmail 64976 invoked from network); 26 Feb 2011 06:39:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Feb 2011 06:39:33 -0000 Received: (qmail 4635 invoked by uid 500); 26 Feb 2011 06:39:33 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 4246 invoked by uid 500); 26 Feb 2011 06:39:30 -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 4238 invoked by uid 99); 26 Feb 2011 06:39:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Feb 2011 06:39:29 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.82.176] (HELO mail-wy0-f176.google.com) (74.125.82.176) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Feb 2011 06:39:24 +0000 Received: by wya21 with SMTP id 21so2896294wya.35 for ; Fri, 25 Feb 2011 22:39:02 -0800 (PST) Received: by 10.217.1.198 with SMTP id n48mr2838896wes.59.1298702342218; Fri, 25 Feb 2011 22:39:02 -0800 (PST) MIME-Version: 1.0 Sender: cos@boudnik.org Received: by 10.216.180.70 with HTTP; Fri, 25 Feb 2011 22:38:42 -0800 (PST) In-Reply-To: References: From: Konstantin Boudnik Date: Fri, 25 Feb 2011 22:38:42 -0800 X-Google-Sender-Auth: bSCngdfVKqhKs1GLLL3D5Hb3YVA Message-ID: Subject: Re: Request: federation JIRA naming? To: hdfs-dev@hadoop.apache.org Cc: suresh srinivas Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Right, if you are looking into email filtering then tagging won't help, I guess. So I guess your solution would work fine. On Fri, Feb 25, 2011 at 21:47, suresh srinivas wrote= : > Having the naming convention that we use helps manage emails better due t= o > subject lines including "HDFS Federation". As far as tagging is concerned= , > all federation jiras are subtasks of HDFS-1052. Hence some kind of groupi= ng > can be done based on that. > > On Fri, Feb 25, 2011 at 4:28 PM, Konstantin Boudnik wrot= e: > >> JIRA has this nice feature called 'Tag'. We've been using this for >> Herriot development - seems much cleaner than clogging synopses field >> with additional wodking. >> -- >> =A0 Take care, >> Konstantin (Cos) Boudnik >> >> >> >> On Fri, Feb 25, 2011 at 14:53, Todd Lipcon wrote: >> > Hey folks, >> > >> > Would those of you working on a branch mind adopting a naming conventi= on >> for >> > all the federation tickets? I'm really glad to see all the changes goi= ng >> > 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 t= o >> > shove off and just deal with it :) >> > >> > -Todd >> > -- >> > Todd Lipcon >> > Software Engineer, Cloudera >> > >> > > > > -- > Regards, > Suresh >