You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Jakob Homan <jg...@gmail.com> on 2011/07/12 03:27:01 UTC
Apache infrastructure has been set up.
Infra has created our infrastructure
(https://issues.apache.org/jira/browse/INFRA-3754).
JIRA is now up at https://issues.apache.org/jira/browse/KAFKA.
Subversion (rw access) is available here:
https://svn.apache.org/repos/asf/incubator/kafka
We can start the initial code drop.
Of note: if we plan to migrate the issues from the old Kafka JIRA, we
need to do so before new issues are created on the Apache JIRA, or the
migration will wipe out the new issues
(https://issues.apache.org/jira/browse/INFRA-3764?focusedCommentId=13062174&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13062174).
Re: Apache infrastructure has been set up.
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Close and re-open issue fixes the problem.
Regards,
Alan
On Jul 20, 2011, at 6:13 PM, Alan D. Cabrera wrote:
> It's weird, if I link a newer issue KAFKA-74 the link looks correct. I delete a "bad" looking link and re-link it and it still has that crossout bar on its link.
>
>
> Regards,
> Alan
>
> On Jul 20, 2011, at 6:09 PM, Jun Rao wrote:
>
>> Yes, I noticed that too. It's confusing.
>>
>> Jun
>>
>> On Wed, Jul 20, 2011 at 5:26 PM, Jakob Homan <jg...@gmail.com> wrote:
>>
>>> Does anyone know why all the issue links are struck out in JIRA, even
>>> if they're not done?
>>> For instance, all the related JIRAs on
>>> https://issues.apache.org/jira/browse/KAFKA-50 are struck out as if
>>> they're done, none of which are. Or is it just me?
>>> -jg
>>>
>>>
>>> On Mon, Jul 11, 2011 at 7:23 PM, Henry Saputra <he...@gmail.com>
>>> wrote:
>>>> Do we need to open a separate INFRA jira case to import the existing
>>>> Kafka existing Jira?
>>>>
>>>> - Henry
>>>>
>>>> On Mon, Jul 11, 2011 at 6:27 PM, Jakob Homan <jg...@gmail.com> wrote:
>>>>> Infra has created our infrastructure
>>>>> (https://issues.apache.org/jira/browse/INFRA-3754).
>>>>> JIRA is now up at https://issues.apache.org/jira/browse/KAFKA.
>>>>> Subversion (rw access) is available here:
>>>>> https://svn.apache.org/repos/asf/incubator/kafka
>>>>>
>>>>> We can start the initial code drop.
>>>>>
>>>>> Of note: if we plan to migrate the issues from the old Kafka JIRA, we
>>>>> need to do so before new issues are created on the Apache JIRA, or the
>>>>> migration will wipe out the new issues
>>>>> (
>>> https://issues.apache.org/jira/browse/INFRA-3764?focusedCommentId=13062174&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13062174
>>> ).
>>>>>
>>>>
>>>
>
Re: Apache infrastructure has been set up.
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
It's weird, if I link a newer issue KAFKA-74 the link looks correct. I delete a "bad" looking link and re-link it and it still has that crossout bar on its link.
Regards,
Alan
On Jul 20, 2011, at 6:09 PM, Jun Rao wrote:
> Yes, I noticed that too. It's confusing.
>
> Jun
>
> On Wed, Jul 20, 2011 at 5:26 PM, Jakob Homan <jg...@gmail.com> wrote:
>
>> Does anyone know why all the issue links are struck out in JIRA, even
>> if they're not done?
>> For instance, all the related JIRAs on
>> https://issues.apache.org/jira/browse/KAFKA-50 are struck out as if
>> they're done, none of which are. Or is it just me?
>> -jg
>>
>>
>> On Mon, Jul 11, 2011 at 7:23 PM, Henry Saputra <he...@gmail.com>
>> wrote:
>>> Do we need to open a separate INFRA jira case to import the existing
>>> Kafka existing Jira?
>>>
>>> - Henry
>>>
>>> On Mon, Jul 11, 2011 at 6:27 PM, Jakob Homan <jg...@gmail.com> wrote:
>>>> Infra has created our infrastructure
>>>> (https://issues.apache.org/jira/browse/INFRA-3754).
>>>> JIRA is now up at https://issues.apache.org/jira/browse/KAFKA.
>>>> Subversion (rw access) is available here:
>>>> https://svn.apache.org/repos/asf/incubator/kafka
>>>>
>>>> We can start the initial code drop.
>>>>
>>>> Of note: if we plan to migrate the issues from the old Kafka JIRA, we
>>>> need to do so before new issues are created on the Apache JIRA, or the
>>>> migration will wipe out the new issues
>>>> (
>> https://issues.apache.org/jira/browse/INFRA-3764?focusedCommentId=13062174&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13062174
>> ).
>>>>
>>>
>>
Re: Apache infrastructure has been set up.
Posted by Jun Rao <ju...@gmail.com>.
Yes, I noticed that too. It's confusing.
Jun
On Wed, Jul 20, 2011 at 5:26 PM, Jakob Homan <jg...@gmail.com> wrote:
> Does anyone know why all the issue links are struck out in JIRA, even
> if they're not done?
> For instance, all the related JIRAs on
> https://issues.apache.org/jira/browse/KAFKA-50 are struck out as if
> they're done, none of which are. Or is it just me?
> -jg
>
>
> On Mon, Jul 11, 2011 at 7:23 PM, Henry Saputra <he...@gmail.com>
> wrote:
> > Do we need to open a separate INFRA jira case to import the existing
> > Kafka existing Jira?
> >
> > - Henry
> >
> > On Mon, Jul 11, 2011 at 6:27 PM, Jakob Homan <jg...@gmail.com> wrote:
> >> Infra has created our infrastructure
> >> (https://issues.apache.org/jira/browse/INFRA-3754).
> >> JIRA is now up at https://issues.apache.org/jira/browse/KAFKA.
> >> Subversion (rw access) is available here:
> >> https://svn.apache.org/repos/asf/incubator/kafka
> >>
> >> We can start the initial code drop.
> >>
> >> Of note: if we plan to migrate the issues from the old Kafka JIRA, we
> >> need to do so before new issues are created on the Apache JIRA, or the
> >> migration will wipe out the new issues
> >> (
> https://issues.apache.org/jira/browse/INFRA-3764?focusedCommentId=13062174&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13062174
> ).
> >>
> >
>
Re: Apache infrastructure has been set up.
Posted by Jakob Homan <jg...@gmail.com>.
Does anyone know why all the issue links are struck out in JIRA, even
if they're not done?
For instance, all the related JIRAs on
https://issues.apache.org/jira/browse/KAFKA-50 are struck out as if
they're done, none of which are. Or is it just me?
-jg
On Mon, Jul 11, 2011 at 7:23 PM, Henry Saputra <he...@gmail.com> wrote:
> Do we need to open a separate INFRA jira case to import the existing
> Kafka existing Jira?
>
> - Henry
>
> On Mon, Jul 11, 2011 at 6:27 PM, Jakob Homan <jg...@gmail.com> wrote:
>> Infra has created our infrastructure
>> (https://issues.apache.org/jira/browse/INFRA-3754).
>> JIRA is now up at https://issues.apache.org/jira/browse/KAFKA.
>> Subversion (rw access) is available here:
>> https://svn.apache.org/repos/asf/incubator/kafka
>>
>> We can start the initial code drop.
>>
>> Of note: if we plan to migrate the issues from the old Kafka JIRA, we
>> need to do so before new issues are created on the Apache JIRA, or the
>> migration will wipe out the new issues
>> (https://issues.apache.org/jira/browse/INFRA-3764?focusedCommentId=13062174&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13062174).
>>
>
Re: Apache infrastructure has been set up.
Posted by Henry Saputra <he...@gmail.com>.
Do we need to open a separate INFRA jira case to import the existing
Kafka existing Jira?
- Henry
On Mon, Jul 11, 2011 at 6:27 PM, Jakob Homan <jg...@gmail.com> wrote:
> Infra has created our infrastructure
> (https://issues.apache.org/jira/browse/INFRA-3754).
> JIRA is now up at https://issues.apache.org/jira/browse/KAFKA.
> Subversion (rw access) is available here:
> https://svn.apache.org/repos/asf/incubator/kafka
>
> We can start the initial code drop.
>
> Of note: if we plan to migrate the issues from the old Kafka JIRA, we
> need to do so before new issues are created on the Apache JIRA, or the
> migration will wipe out the new issues
> (https://issues.apache.org/jira/browse/INFRA-3764?focusedCommentId=13062174&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13062174).
>