qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carl Trieloff <cctriel...@redhat.com>
Subject Re: populating JIRA
Date Tue, 10 Oct 2006 22:53:26 GMT

No it needs to be done in both... if you close something in one language 
only then clone the JIRA for the
other language. If you do it for both then just close the JIRA.

Carl.

John O'Hara wrote:
> We need to understand how to deal with features in the Java and C++ 
> brokers.
>
> Is it done when its done in one of them?
>
> John
>
> On 10/10/06, Robert Greig <robert.j.greig@gmail.com> wrote:
>>
>> On 10/10/06, John O'Hara <john.r.ohara@gmail.com> wrote:
>> > These spring to mind:
>> > 1) Complete local transaction support (XA not urgent at all)
>>
>> What do think is missing?
>>
>> > 3) Staging for larger messages (will benefit from the work 
>> happening on
>> the
>> > protocol content classes over at AMQP.ORG)
>>
>> This is part of QPID-17 which I am working on.
>>
>> > 4) JMS Compliance (approximate first so people familiar with JMS don't
>> get
>> > surprises; not aiming for TCK compliance of any sort on a first run,
>> plus we
>> > don't have the TCK :-)
>>
>> We are doing pretty well on JMS compliance. The major outstanding item
>> is message selectors which we have discussed at some length on the
>> list. I will raise a Jira for it. We also need queue browsing which
>> has been discussed before and I think will "come out in the wash" with
>> our content class redesign proposal.
>>
>> RG
>>
>


Mime
View raw message