You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Stephen Connolly <st...@gmail.com> on 2011/06/01 12:21:43 UTC
[RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
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
RE: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Gavin McDonald <ga...@16degrees.com.au>.
I've already been talking with Ben and Brett about this for some time, some
of what
has been written in this thread has not been mentioned by Ben to me before,
so I'll
get some more clarifications from him, otherwise infra will be glad to help
migrate
over the Maven and associated Jiras and as part of Infra, I'll lead that
effort to do the
deed at this end.
I'll join the Maven dev list now so we can communicate better as the run up
to the move
occurs.
Thanks
Gav...
> -----Original Message-----
> From: Dennis Lundberg [mailto:dennisl@apache.org]
> Sent: Monday, 6 June 2011 6:35 PM
> To: Stephen Connolly
> Cc: infrastructure@apache.org; Maven Developers List
> Subject: Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to
> issues.apache.org
>
> Hi
>
> I've got an email similar to this that's been sitting in my draft box for
a couple
> of weeks. Here's what I originally wrote in it:
>
> ---
>
> This has come up from time to time, and I think now is as good a time as
any
> to get the ball rolling on this. I've done a fair bit of JIRA
administration and a
> couple of migrations from other issue tracker, so I'm willing to take on
part of
> the workload if people are OK with that.
>
> First I'd like to say that I have had no issues with having JIRA over at
> Codehaus. Their service and uptime have been great. However, it has been
> asked on numerous occasions:
>
> Isn't ASF infra good enough for the Maven project?
>
> My answer to that has always been: of course they are. They also do an
> excellent job. The reservations I've had have been more practical.
>
> We have *a lot* of JIRA project over at Codehaus [1], so we need some kind
> of road map for this.
>
>
> [1]
> http://jira.codehaus.org/secure/BrowseProjects.jspa#10004
> http://jira.codehaus.org/secure/BrowseProjects.jspa#10060
> http://jira.codehaus.org/secure/BrowseProjects.jspa#10062
> http://jira.codehaus.org/secure/BrowseProjects.jspa#10061
>
> ---
>
>
> I won't reiterate the pros and cons, but my feeling is that this is
something
> that the ASF wants us to do. If the ASF is willing to take the cons (lots
of new
> JIRA users) with the pros, then I say let's do it. The longer we wait the
more
> difficult it will be.
>
>
>
> On 2011-06-01 12:21, 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
> >
>
>
> --
> Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Dennis Lundberg <de...@apache.org>.
Hi
I've got an email similar to this that's been sitting in my draft box
for a couple of weeks. Here's what I originally wrote in it:
---
This has come up from time to time, and I think now is as good a time as
any to get the ball rolling on this. I've done a fair bit of JIRA
administration and a couple of migrations from other issue tracker, so
I'm willing to take on part of the workload if people are OK with that.
First I'd like to say that I have had no issues with having JIRA over at
Codehaus. Their service and uptime have been great. However, it has been
asked on numerous occasions:
Isn't ASF infra good enough for the Maven project?
My answer to that has always been: of course they are. They also do an
excellent job. The reservations I've had have been more practical.
We have *a lot* of JIRA project over at Codehaus [1], so we need some
kind of road map for this.
[1]
http://jira.codehaus.org/secure/BrowseProjects.jspa#10004
http://jira.codehaus.org/secure/BrowseProjects.jspa#10060
http://jira.codehaus.org/secure/BrowseProjects.jspa#10062
http://jira.codehaus.org/secure/BrowseProjects.jspa#10061
---
I won't reiterate the pros and cons, but my feeling is that this is
something that the ASF wants us to do. If the ASF is willing to take the
cons (lots of new JIRA users) with the pros, then I say let's do it. The
longer we wait the more difficult it will be.
On 2011-06-01 12:21, 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
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Benson Margulies <bi...@gmail.com>.
Wearing an Apache Member hat (in no particular order)
1) IP. Patches at Apache JIRA are more clearly contributed to the foundation.
2) Appearances: Maven is an Apache project. As part of brand
management, it's infrastructure should be at Apache.
3) Interdependencies to other Apache project. We should have them.
On Wed, Jun 1, 2011 at 7:02 AM, Lukas Theussl <lt...@apache.org> wrote:
>
> well, you had 1 point under +1 and two points under -1, so that's one more
> under -1... ;)
>
> I understand that this is not a vote, simply my opinion. I just don't see
> the point of going through all this hassle if the only gain is to be hosted
> on different hardware. What's wrong with codehaus? What do we gain at
> Apache?
>
> -Lukas
>
>
> Stephen Connolly wrote:
>>
>> Can you please iterate your cons...
>>
>> I want to summarize at the end and then the PMC will decide what the
>> next action is
>>
>> On 1 June 2011 11:39, Lukas Theussl<lt...@apache.org> wrote:
>>>
>>>
>>> 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
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Lukas Theussl <lt...@apache.org>.
well, you had 1 point under +1 and two points under -1, so that's one
more under -1... ;)
I understand that this is not a vote, simply my opinion. I just don't
see the point of going through all this hassle if the only gain is to be
hosted on different hardware. What's wrong with codehaus? What do we
gain at Apache?
-Lukas
Stephen Connolly wrote:
> Can you please iterate your cons...
>
> I want to summarize at the end and then the PMC will decide what the
> next action is
>
> On 1 June 2011 11:39, Lukas Theussl<lt...@apache.org> wrote:
>>
>>
>> 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
>>
>>
>
> ---------------------------------------------------------------------
> 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
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Stephen Connolly <st...@gmail.com>.
Can you please iterate your cons...
I want to summarize at the end and then the PMC will decide what the
next action is
On 1 June 2011 11:39, Lukas Theussl <lt...@apache.org> wrote:
>
>
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Lukas Theussl <lt...@apache.org>.
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
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by sebb <se...@gmail.com>.
Does Codehaus JIRA support adding SVN commit messages to issues?
I've yet to see any such entries, but in the ASF JIRA this is used extensively.
IMO it's a very useful feature - makes it much easier to follow what
happened to an issue later on.
I don't know whether the feature is not available, not enabled or just
not being used in Codehaus JIRA, but on the face of it the ASF JIRA is
better in this respect.
On 2 June 2011 15:00, Brian Fox <br...@infinity.nu> wrote:
> I did the m2e move a few years back from codehaus to sonatype and it
> was definititely non-trivial. You have to line up the workflows and
> fields on both sides and then you have to contend with all the user
> accounts that get thrown into Jira.
>
> 2011/6/1 Arnaud Héritier <ah...@gmail.com>:
>> +0.
>>
>> Even if it could be the best for us to have coherent systems such migration
>> is very difficult to do as Jira provides very few things to do such changes.
>> The export/import by project isn't transitive with all Jira internal
>> elements (users, groups, workflows, schemes ....).
>> It is AFAIK very difficult to do and many tasks have to be done manually (or
>> we have to write ourself some tooling).
>> During the migration process we'll have to close the codehaus service thus
>> we have to take care to not let our community without issues trackers for
>> several days.
>>
>> Who should work on this migration ? ASF infra ? The dev team ?
>>
>> If it's the infra team, I say +0,5
>> If it's us, -0,5 (I'm not sure we have enough resources to do it for now)
>>
>> Arnaud
>>
>>
>>
>> On Wed, Jun 1, 2011 at 4:49 PM, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>>> On 1 June 2011 14:46, Brett Porter <br...@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
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> 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
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Brian Fox <br...@infinity.nu>.
I did the m2e move a few years back from codehaus to sonatype and it
was definititely non-trivial. You have to line up the workflows and
fields on both sides and then you have to contend with all the user
accounts that get thrown into Jira.
2011/6/1 Arnaud Héritier <ah...@gmail.com>:
> +0.
>
> Even if it could be the best for us to have coherent systems such migration
> is very difficult to do as Jira provides very few things to do such changes.
> The export/import by project isn't transitive with all Jira internal
> elements (users, groups, workflows, schemes ....).
> It is AFAIK very difficult to do and many tasks have to be done manually (or
> we have to write ourself some tooling).
> During the migration process we'll have to close the codehaus service thus
> we have to take care to not let our community without issues trackers for
> several days.
>
> Who should work on this migration ? ASF infra ? The dev team ?
>
> If it's the infra team, I say +0,5
> If it's us, -0,5 (I'm not sure we have enough resources to do it for now)
>
> Arnaud
>
>
>
> On Wed, Jun 1, 2011 at 4:49 PM, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
>
>> On 1 June 2011 14:46, Brett Porter <br...@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
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Arnaud Héritier <ah...@gmail.com>.
+0.
Even if it could be the best for us to have coherent systems such migration
is very difficult to do as Jira provides very few things to do such changes.
The export/import by project isn't transitive with all Jira internal
elements (users, groups, workflows, schemes ....).
It is AFAIK very difficult to do and many tasks have to be done manually (or
we have to write ourself some tooling).
During the migration process we'll have to close the codehaus service thus
we have to take care to not let our community without issues trackers for
several days.
Who should work on this migration ? ASF infra ? The dev team ?
If it's the infra team, I say +0,5
If it's us, -0,5 (I'm not sure we have enough resources to do it for now)
Arnaud
On Wed, Jun 1, 2011 at 4:49 PM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> On 1 June 2011 14:46, Brett Porter <br...@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
>
>
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Stephen Connolly <st...@gmail.com>.
On 1 June 2011 14:46, Brett Porter <br...@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
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by sebb <se...@gmail.com>.
On 1 June 2011 14:46, Brett Porter <br...@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.
>
>>
>> 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 :)
I disagree - I think that argument would apply to moving from JIRA to
some other issue tracker, not to moving to a different host and JIRA
version.
Besides, the current arrangement is not perfect, as has already been described.
>>
>> 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
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Brett Porter <br...@apache.org>.
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.
>
> 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
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Olivier Lamy <ol...@apache.org>.
Agree.
BTW we have to think to migrate some linked projects (Archiva MRM,
Continuum CONTINUUM).
And if we could have the same keys (MNG, SCM etc), Ben could maybe add
a rewrite or redirect rule to help users going to jira @asf.
The only trouble I see is watchers,reporters who doesn't exists @asf.
2011/6/1 Stephen Connolly <st...@gmail.com>:
> 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
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://www.linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Stephen Connolly <st...@gmail.com>.
This is not a vote BTW
On 1 June 2011 11:25, Mark Struberg <st...@yahoo.de> wrote:
> +1
>
> the problem with cross referencing already exists on the other side too. I e.g. cannot link from a WAGON-329 (hosted at codehaus atm) to FTPSERVER-413 (hosted at apache).
>
> LieGrue,
> strub
>
> --- On Wed, 6/1/11, Stephen Connolly <st...@gmail.com> wrote:
>
>> From: Stephen Connolly <st...@gmail.com>
>> Subject: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
>> To: infrastructure@apache.org, "Maven Developers List" <de...@maven.apache.org>
>> Date: Wednesday, June 1, 2011, 10:21 AM
>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
Posted by Mark Struberg <st...@yahoo.de>.
+1
the problem with cross referencing already exists on the other side too. I e.g. cannot link from a WAGON-329 (hosted at codehaus atm) to FTPSERVER-413 (hosted at apache).
LieGrue,
strub
--- On Wed, 6/1/11, Stephen Connolly <st...@gmail.com> wrote:
> From: Stephen Connolly <st...@gmail.com>
> Subject: [RFC] Migrating Maven JIRA from jira.codehaus.org to issues.apache.org
> To: infrastructure@apache.org, "Maven Developers List" <de...@maven.apache.org>
> Date: Wednesday, June 1, 2011, 10:21 AM
> 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