You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Jonathan Hsieh <jo...@cloudera.com> on 2011/06/27 20:33:54 UTC
Prexisting Jiras [was Re: Plans for moving mailing lists over to apache.]
On Fri, Jun 24, 2011 at 11:30 AM, Jonathan Hsieh <jo...@cloudera.com> wrote:
>
>
> On Thu, Jun 23, 2011 at 11:12 PM, Ralph Goers <ra...@dslextreme.com>wrote:
>
>>
>> >
>> > One major concern that I have is that I'd like to be able to port
>> history of
>> > the repo and history of the jira into the new jira and svn repo. While
>> > porting the repo history would be nice, I'd really really woud like to
>> being
>> > able to port the JIRA history. I think a lot of folks would find it
>> painful
>> > to restart the JIRA with the same JIRA numbers, or re-enter known
>> issues, or
>> > rehash previous designs conversations.
>>
>> Maven has had its Jira at codehaus for a long time and wants to move to
>> the ASF's Jira but is facing the same issue. From what I gathered moving
>> the issues over is possible but I don't think you will get the same numbers.
>> However, I believe it may take work to extract just the issues for a single
>> component.
>>
>>
> I'm willing to explore this -- there are many issues that have accrued over
> time. I think in the worst case situation we somehow bump the apache jira
> to start from 1000 and port issues from the old repo over just so that there
> will be less confusion (I'm thinking about the "google for a patch" scenario
> where it exists in two differnt places with two different meanings.)
>
>
Interesting. Maven never moved their jira to apache's jira (or since maven
did this in 2003, and it looks like issues.apache.org/jira/ showed up in
2004 so they may have been grandfathered) . It still lives on Codehaus, has
been there for the past year and seems to be actively continuing along that
path. (for maven 2.x and maven 3.x). Was this attempt to move something
that happened recently or a long time ago?
I'm not advocating for it, but would that be an option for us? (I
personally don't like it).
Searching for more examples... before I go to infra...
Jon.
--
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// jon@cloudera.com
Re: Prexisting Jiras [was Re: Plans for moving mailing lists over to apache.]
Posted by Ralph Goers <ra...@dslextreme.com>.
On Jun 27, 2011, at 11:33 AM, Jonathan Hsieh wrote:
> On Fri, Jun 24, 2011 at 11:30 AM, Jonathan Hsieh <jo...@cloudera.com> wrote:
>
>>
>>
>> On Thu, Jun 23, 2011 at 11:12 PM, Ralph Goers <ra...@dslextreme.com>wrote:
>>
>>>
>>>>
>>>> One major concern that I have is that I'd like to be able to port
>>> history of
>>>> the repo and history of the jira into the new jira and svn repo. While
>>>> porting the repo history would be nice, I'd really really woud like to
>>> being
>>>> able to port the JIRA history. I think a lot of folks would find it
>>> painful
>>>> to restart the JIRA with the same JIRA numbers, or re-enter known
>>> issues, or
>>>> rehash previous designs conversations.
>>>
>>> Maven has had its Jira at codehaus for a long time and wants to move to
>>> the ASF's Jira but is facing the same issue. From what I gathered moving
>>> the issues over is possible but I don't think you will get the same numbers.
>>> However, I believe it may take work to extract just the issues for a single
>>> component.
>>>
>>>
>> I'm willing to explore this -- there are many issues that have accrued over
>> time. I think in the worst case situation we somehow bump the apache jira
>> to start from 1000 and port issues from the old repo over just so that there
>> will be less confusion (I'm thinking about the "google for a patch" scenario
>> where it exists in two differnt places with two different meanings.)
>>
>>
> Interesting. Maven never moved their jira to apache's jira (or since maven
> did this in 2003, and it looks like issues.apache.org/jira/ showed up in
> 2004 so they may have been grandfathered) . It still lives on Codehaus, has
> been there for the past year and seems to be actively continuing along that
> path. (for maven 2.x and maven 3.x). Was this attempt to move something
> that happened recently or a long time ago?
>
> I'm not advocating for it, but would that be an option for us? (I
> personally don't like it).
>
> Searching for more examples... before I go to infra...
The Maven community has talked about moving to the Apache Jira for a while. However, the ASF Jira was an older version than the one at codehaus so moving couldn't happen. Recently they have both been brought up to the same version so the discussion came up again. Really, they would prefer to move but the amount of work involved for such a large project may not make it practical.
Ralph