Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of ltheussl@gmail.com designates
 209.85.161.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:message-id:date:from:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=i1S7+47/z7Mikzss3ylcqKXWwclrF3tlhojBXp5YLXCn1G/b5I6s6PL7K4UoqkGXwF
         xWy0P9WF+lV5+yxvzI+cRW7vcnBvyg8TDkj0JpVoWWIZlNc56bIQoOasvwcsItidq0fs
         ynLF1Ui7vnByI7m9ZlmzqtqNlSX+7JEmgfmIc=
Sender: Lukas Theussl <ltheussl@gmail.com>
Message-ID: <4DE616D7.2010806@apache.org>
Date: Wed, 01 Jun 2011 12:39:19 +0200
From: Lukas Theussl <ltheussl@apache.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.16) Gecko/20101206 SeaMonkey/2.0.11
MIME-Version: 1.0
To: Maven Developers List <dev@maven.apache.org>
Subject: Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to
 issues.apache.org
References: <BANLkTimZ+u0AB-6c9=Fnoc4dKi1npuFOvg@mail.gmail.com>
In-Reply-To: <BANLkTimZ+u0AB-6c9=Fnoc4dKi1npuFOvg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


I see more cons than pros, plus: potential trouble, potential confusion, 
lots of hassle.

-1

-Lukas


Stephen Connolly wrote:
> REQUEST FOR COMMENTS: Potential migration of Maven's JIRA from
> jira.codehaus.org to issues.apache.org
>
> Just wondering now that codehaus and apache are on nearly similar
> versions (4.1.2 and 4.2.4 respectively) what would be involved.
>
> Ben@codehaus can give us a 4.1.2 dump of the entire codehaus jira and
> we'd just have to cull out the non-maven projects (easier way than any
> others is what Ben thinks as most of the projects are Maven based
> projects)
>
> On the Infra side, would this be the easiest way to pull the issues in?
>
> What do people think in general?
>
> +1's:
>   * We'd be fully on Apache controlled hardware
>
> -1's:
>   * Since a lot of the issues end up being actually issues in a lower
> layer (most of which if not ASF hosted live/lived @ codehaus) or an
> upper layer (i.e. one of the mojo plugins) we'd loose the ability to
> move those issues to the correct project and instead we'd have to
> create a new tracking issue on the root cause project's jira
>   * What we have works, if it ain't broke don't fix it
>
> Once we have enough comments/feedback (I'm willing to give a week or
> two), I'll put the options to the Maven PMC who will ultimately EITHER
> make a decision OR delegate making a decision to all the Maven
> committers.
>
> -Stephen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org