You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Kumar Sundaram <su...@hotmail.com> on 2011/07/15 23:30:44 UTC
QPID-2784: like to work on this
i have joined this group very recently, picked the JIRA, but who
will assign to me, so that i could work on. I would like to work on
https://issues.apache.org/jira/browse/QPID-2784
Thanks
Kumar
----- Original Message -----
From: <jr...@redhat.com>
To: <de...@qpid.apache.org>
Sent: Friday, July 15, 2011 2:38 PM
Subject: Re: 0.12 release update - release branch created, beta available
> Well, it already is namespaced. We're exploiting the full power of the
> internet: hierarchical domain names in mail addresses. That's
> namespacing, and I know from personal experience that it serves nicely for
> mail filters.
>
> Justin
>
> On Fri, 15 Jul 2011, Kumar Sundaram wrote:
>
>> 1. . Help you set the efficient filter
>> curently i am using as filter "qpid.apache.org" , need better keyword
>> on subject
>> QPID-release
>> QPID-review
>>
>> 2. for example
>> JIRA does the preifx as [jir][Updated | Resolved | Assigned |
>> Commented])(QPID-\d\d\d\d) (\s)*
>>
>> 3. Mangeabillity issue raise, when the email orginated from Indiviual
>> with subject alone without any keyword prefix are diffcult to manage.
>>
>> 4. Effiecient way to manage the proliferation of emails,
>> its same idea as programming languages has ( Scope/ namespace/
>> package ) or Context
>>
>>
>> Thanks
>> Kumar
>>
>>
>>
>> ----- Original Message ----- From: "Justin Ross" <ju...@redhat.com>
>> To: <de...@qpid.apache.org>
>> Sent: Friday, July 15, 2011 10:47 AM
>> Subject: Re: 0.12 release update - release branch created, beta available
>>
>>
>>> Out of curiosity, what problem would that solve for you? Every message
>>> to dev@qpid.apache.org is related to Qpid.
>>>
>>> Justin
>>>
>>> On Fri, 15 Jul 2011, Kumar Sundaram wrote:
>>>
>>>> I would like to propose any email related QPID from individual prefix
>>>> the subject with QPID:
>>>> For example, the following email thread, was started with subject
>>>> " 0.12 release update - release branch created, beta available "
>>>> change the subject to
>>>> QPID: 0.12 release update - release branch created, beta available
>>>>
>>>> in the same way
>>>> QPID: Review Request: Recreation of JCA Resource Adapter review
>>>>
>>>> Kumar
>>>>
>>>> ----- Original Message ----- From: "Rajith Attapattu"
>>>> <ra...@gmail.com>
>>>> To: <de...@qpid.apache.org>
>>>> Sent: Thursday, July 14, 2011 5:36 PM
>>>> Subject: Re: 0.12 release update - release branch created, beta
>>>> available
>>>>
>>>>
>>>> On Thu, Jul 14, 2011 at 2:56 PM, Justin Ross <jr...@redhat.com> wrote:
>>>>> Rajith, I'm confused by this one. All the commits associated with
>>>>> QPID-3302 fall before the 0.12 branch point, 1141543. I figure we've
>>>>> already got these in 0.12.
>>>> Oh dear, my bad. I was under the impression it was not.
>>>> I guess I got confused with the alpha release. I believe this was
>>>> after the alpha, but forgot that you didn't branch until after that.
>>>> Again please accept my apologies !
>>>>
>>>> Rajith
>>>>
>>>>> Justin
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Rajith Attapattu" <ra...@gmail.com>
>>>>> To: dev@qpid.apache.org
>>>>> Sent: Thursday, July 14, 2011 10:50:18 AM
>>>>> Subject: Re: 0.12 release update - release branch created, beta
>>>>> available
>>>>>
>>>>> Justin,
>>>>>
>>>>> Could we apply the fix for QPID-3302 into the release branch ?
>>>>> It's a very low impact change and it allows folks to use JMS to do QMF
>>>>> operations via Map messages.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Rajith
>>>>>
>>>>> On Tue, Jul 12, 2011 at 1:31 PM, Chuck Rolke <cr...@redhat.com>
>>>>> wrote:
>>>>>> +1 Ship it.
>>>>>>
>>>>>> -Chuck
>>>>>>
>>>>>> ----- Original Message -----
>>>>>>> From: "Cliff Jansen" <cl...@gmail.com>
>>>>>>> To: dev@qpid.apache.org
>>>>>>> Sent: Tuesday, July 12, 2011 1:21:57 PM
>>>>>>> Subject: Re: 0.12 release update - release branch created, beta
>>>>>>> available
>>>>>>> I have tested the patch for QPID-3338 against qpid-0.12-beta on
>>>>>>> Linux
>>>>>>> and it appears to do the right thing for mingw and cmake.
>>>>>>>
>>>>>>> I would like to request approval for this patch.
>>>>>>>
>>>>>>> cliff
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>> Project: http://qpid.apache.org
>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>> Project: http://qpid.apache.org
>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>> Project: http://qpid.apache.org
>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>> Project: http://qpid.apache.org
>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> Apache Qpid - AMQP Messaging Implementation
>>>> Project: http://qpid.apache.org
>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> Apache Qpid - AMQP Messaging Implementation
>>>> Project: http://qpid.apache.org
>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> Apache Qpid - AMQP Messaging Implementation
>>> Project: http://qpid.apache.org
>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: QPID-2784: like to work on this
Posted by Steve Huston <sh...@riverace.com>.
Hi Kumar,
Thank you for your offer and enthusiasm. I believe that jiras can only be
assigned to committers. However, please go ahead and do whatever work you
can and attach any changes as patches to the jira. Be sure to check the
"license to Apache" box when you attach your patches.
Thank you,
-Steve Huston
-----Original Message-----
From: Kumar Sundaram [mailto:sundaramkumar@hotmail.com]
Sent: Friday, July 15, 2011 5:31 PM
To: dev@qpid.apache.org
Subject: QPID-2784: like to work on this
i have joined this group very recently, picked the JIRA, but who will
assign to me, so that i could work on. I would like to work on
https://issues.apache.org/jira/browse/QPID-2784
Thanks
Kumar
----- Original Message -----
From: <jr...@redhat.com>
To: <de...@qpid.apache.org>
Sent: Friday, July 15, 2011 2:38 PM
Subject: Re: 0.12 release update - release branch created, beta available
> Well, it already is namespaced. We're exploiting the full power of the
> internet: hierarchical domain names in mail addresses. That's
> namespacing, and I know from personal experience that it serves nicely for
> mail filters.
>
> Justin
>
> On Fri, 15 Jul 2011, Kumar Sundaram wrote:
>
>> 1. . Help you set the efficient filter
>> curently i am using as filter "qpid.apache.org" , need better keyword
>> on subject
>> QPID-release
>> QPID-review
>>
>> 2. for example
>> JIRA does the preifx as [jir][Updated | Resolved | Assigned |
>> Commented])(QPID-\d\d\d\d) (\s)*
>>
>> 3. Mangeabillity issue raise, when the email orginated from Indiviual
>> with subject alone without any keyword prefix are diffcult to manage.
>>
>> 4. Effiecient way to manage the proliferation of emails,
>> its same idea as programming languages has ( Scope/ namespace/
>> package ) or Context
>>
>>
>> Thanks
>> Kumar
>>
>>
>>
>> ----- Original Message ----- From: "Justin Ross" <ju...@redhat.com>
>> To: <de...@qpid.apache.org>
>> Sent: Friday, July 15, 2011 10:47 AM
>> Subject: Re: 0.12 release update - release branch created, beta available
>>
>>
>>> Out of curiosity, what problem would that solve for you? Every message
>>> to dev@qpid.apache.org is related to Qpid.
>>>
>>> Justin
>>>
>>> On Fri, 15 Jul 2011, Kumar Sundaram wrote:
>>>
>>>> I would like to propose any email related QPID from individual prefix
>>>> the subject with QPID:
>>>> For example, the following email thread, was started with subject
>>>> " 0.12 release update - release branch created, beta available "
>>>> change the subject to
>>>> QPID: 0.12 release update - release branch created, beta available
>>>>
>>>> in the same way
>>>> QPID: Review Request: Recreation of JCA Resource Adapter review
>>>>
>>>> Kumar
>>>>
>>>> ----- Original Message ----- From: "Rajith Attapattu"
>>>> <ra...@gmail.com>
>>>> To: <de...@qpid.apache.org>
>>>> Sent: Thursday, July 14, 2011 5:36 PM
>>>> Subject: Re: 0.12 release update - release branch created, beta
>>>> available
>>>>
>>>>
>>>> On Thu, Jul 14, 2011 at 2:56 PM, Justin Ross <jr...@redhat.com> wrote:
>>>>> Rajith, I'm confused by this one. All the commits associated with
>>>>> QPID-3302 fall before the 0.12 branch point, 1141543. I figure we've
>>>>> already got these in 0.12.
>>>> Oh dear, my bad. I was under the impression it was not.
>>>> I guess I got confused with the alpha release. I believe this was
>>>> after the alpha, but forgot that you didn't branch until after that.
>>>> Again please accept my apologies !
>>>>
>>>> Rajith
>>>>
>>>>> Justin
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Rajith Attapattu" <ra...@gmail.com>
>>>>> To: dev@qpid.apache.org
>>>>> Sent: Thursday, July 14, 2011 10:50:18 AM
>>>>> Subject: Re: 0.12 release update - release branch created, beta
>>>>> available
>>>>>
>>>>> Justin,
>>>>>
>>>>> Could we apply the fix for QPID-3302 into the release branch ?
>>>>> It's a very low impact change and it allows folks to use JMS to do QMF
>>>>> operations via Map messages.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Rajith
>>>>>
>>>>> On Tue, Jul 12, 2011 at 1:31 PM, Chuck Rolke <cr...@redhat.com>
>>>>> wrote:
>>>>>> +1 Ship it.
>>>>>>
>>>>>> -Chuck
>>>>>>
>>>>>> ----- Original Message -----
>>>>>>> From: "Cliff Jansen" <cl...@gmail.com>
>>>>>>> To: dev@qpid.apache.org
>>>>>>> Sent: Tuesday, July 12, 2011 1:21:57 PM
>>>>>>> Subject: Re: 0.12 release update - release branch created, beta
>>>>>>> available
>>>>>>> I have tested the patch for QPID-3338 against qpid-0.12-beta on
>>>>>>> Linux
>>>>>>> and it appears to do the right thing for mingw and cmake.
>>>>>>>
>>>>>>> I would like to request approval for this patch.
>>>>>>>
>>>>>>> cliff
>>>>>>>
>>>>>>>
---------------------------------------------------------------------
>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>> Project: http://qpid.apache.org
>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>> Project: http://qpid.apache.org
>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>> Project: http://qpid.apache.org
>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>> Project: http://qpid.apache.org
>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> Apache Qpid - AMQP Messaging Implementation
>>>> Project: http://qpid.apache.org
>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> Apache Qpid - AMQP Messaging Implementation
>>>> Project: http://qpid.apache.org
>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> Apache Qpid - AMQP Messaging Implementation
>>> Project: http://qpid.apache.org
>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org