Return-Path: 
 <dev-return-46602-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
X-Original-To: apmail-directory-dev-archive@www.apache.org
Delivered-To: apmail-directory-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 55399176B3
	for <apmail-directory-dev-archive@www.apache.org>;
 Fri, 21 Nov 2014 21:14:43 +0000 (UTC)
Received: (qmail 17273 invoked by uid 500); 21 Nov 2014 21:14:43 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 17236 invoked by uid 500); 21 Nov 2014 21:14:43 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 17226 invoked by uid 99); 21 Nov 2014 21:14:42 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Nov 2014 21:14:42 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com
 designates 209.85.212.178 as permitted sender)
Received: from [209.85.212.178] (HELO mail-wi0-f178.google.com)
 (209.85.212.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Nov 2014 21:14:36 +0000
Received: by mail-wi0-f178.google.com with SMTP id hi2so482303wib.17
        for <dev@directory.apache.org>; Fri, 21 Nov 2014 13:12:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        bh=1AI/phPl7+g1U1fg1xOBCBvhcK5FYI8Yix11Mxm+QsY=;
        b=Y54UoIgXAT8PvqqYNvEHSHyXYgl1dUNshglcw99sX6PaR18Pz5Vnj08SiMgKP1kzJw
         MbkAucegKHFSCgHbeFOsYtJV52x+kZ81+u5Q1rMWdym5DNt2n8wgFfP+2WMOxI9Fdpc1
         PnWL+8iV35U5zeztT1babk30+mmATWs/3fgbinEI2MhZR0LpbBaYJMGeD6TeHnYY5aHZ
         WnIkiojd3og+j/SGYenwvVHHCiXVCHhesGHXda3PJsjLe5iKbjtZ1sfa95oaMPlgGKsT
         C9GzjXjTn/UsFQHMygt1EVm02ZWXnxojJh+A8Y8neAyPKSdlZnyd4tKbJxVb6wIy/jf2
         tZaw==
X-Received: by 10.181.12.17 with SMTP id em17mr318878wid.45.1416604365280;
        Fri, 21 Nov 2014 13:12:45 -0800 (PST)
Received: from [192.168.1.19]
 (AMontsouris-651-1-255-227.w92-163.abo.wanadoo.fr. [92.163.86.227])
        by mx.google.com with ESMTPSA id jp3sm665680wid.9.2014.11.21.13.12.43
        for <dev@directory.apache.org>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Fri, 21 Nov 2014 13:12:44 -0800 (PST)
Message-ID: <546FAACC.1040805@gmail.com>
Date: Fri, 21 Nov 2014 22:12:44 +0100
From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= <elecharny@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: [Fortress] Multiple JIRA vs one single JIRA
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi guys,

today, Gavn asked me if there is any valid reason for having more than
one JIRA for Fortress. I thought that this was a valid question, and
thinking about it, I don't see why we should have more than one JIRA
(FORTRESS). We may want to rename FORTRESS-CORE JIRA to simply FORTRESS.

Thoughts ?