maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Date Wed, 01 Jun 2011 14:49:22 GMT
On 1 June 2011 14:46, Brett Porter <brett@apache.org> wrote:
> On 01/06/2011, at 8:21 PM, 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?
>
> I'd been meaning to mention...
>
> As it happens, Archiva & Continuum are moving their issues over already, so I have
already asked Ben if he can include the Maven projects in the same test dump. That doesn't
imply any commitment - they can be deleted before import - but it means we can have a look
at how it would turn out.

Yeah, Ben told me that already!

>
>>
>> What do people think in general?
>>
>> +1's:
>> * We'd be fully on Apache controlled hardware
>
> Some other advantages:
> - it's what some new users expect (I've had some small complaints over time about not
finding it / needing another account on a different JIRA)
> - the subversion commits tab would work again
> - takes the load of Ben & Codehaus :)
>
>>
>> -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
>
> I don't see that that's a big issue.
>
>> * What we have works, if it ain't broke don't fix it
>
> That's a pretty powerful one :)
>
>>
>> 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
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
>
> ---------------------------------------------------------------------
> 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


Mime
View raw message