German Shepherd created PROTON-733:
--
Summary: SASL related updates (wishes)
Key: PROTON-733
URL: https://issues.apache.org/jira/browse/PROTON-733
Project: Qpid Proton
Issue Type: Wish
[
https://issues.apache.org/jira/browse/PROTON-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
German Shepherd closed PROTON-725.
--
Resolution: Not a Problem
Fix Version/s: 0.8
Let me provide an update.
MS Azure does act
Gordon Sim created PROTON-734:
-
Summary: deliveries are not returned in order
Key: PROTON-734
URL: https://issues.apache.org/jira/browse/PROTON-734
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-724.
Resolution: Fixed
Fix Version/s: 0.8
> pn_transport_close_head doesn't genera
[
https://issues.apache.org/jira/browse/PROTON-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-729.
Resolution: Fixed
> library assers in pn_full_settle
> -
Hey Rafi - thanks for doing this.
Can we add support for Python 3 in the timeline?
- Original Message -
> From: "Rafael Schloming"
> To: proton@qpid.apache.org, d...@qpid.apache.org, us...@qpid.apache.org
> Sent: Tuesday, October 28, 2014 3:59:53 PM
> Subject: Proton release planning
>
[ X ] Yes, release Proton 0.8 RC5 as 0.8 final
I tested 0.8 against the Dispatch trunk.
On 10/27/2014 09:51 PM, Rafael Schloming wrote:
> Hi Everyone,
>
> Sorry for the delay, there seemed to be some kind of Nexus outage today, so
> I was unable to generate the java binaries until just now.
>
>
Is the plan to keep JMS in a separate project and managed separately as
part of qpid? How are the dependencies between Proton and Qpid-JMS going
to be addressed?
Jack
On 10/29/14, 9:13 AM, "Ken Giusti" wrote:
>Hey Rafi - thanks for doing this.
>
>Can we add support for Python 3 in the tim
[X} Yes, release Proton 0.8 RC5 as 0.8 final
I tested 0.8 against the HornetQ trunk. Had to rename a few enums (SESSION_OPEN
to SESSION_LOCAL_OPEN) but other than that everything worked.
On Wed, Oct 29, 2014 at 10:13 AM, Ken Giusti wrote:
> Hey Rafi - thanks for doing this.
>
> Can we add support for Python 3 in the timeline?
>
Without a patch or some exploratory work on it, I'm not really sure where
I'd slot it in.
--Rafael
[
https://issues.apache.org/jira/browse/PROTON-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14188840#comment-14188840
]
ASF subversion and git services commented on PROTON-723:
Commit 16
[
https://issues.apache.org/jira/browse/PROTON-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-723.
Resolution: Fixed
Fix Version/s: 0.9
> Proton-c does not support attaching to
[
https://issues.apache.org/jira/browse/PROTON-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated PROTON-731:
Attachment: 0001-PROTON-731-Installing-Python-requires-Proton-be-inst.patch
Changes both CHE
[ x ] Yes, release Proton 0.8 RC5 as 0.8 final
Tested on Windows: 32/64 bit, XP/Win8.1
On Monday, October 27, 2014, Rafael Schloming wrote:
> Hi Everyone,
>
> Sorry for the delay, there seemed to be some kind of Nexus outage today, so
> I was unable to generate the java binaries until just now.
[ X ] Yes, release Proton 0.8 RC5 as 0.8 final
Tested Windows Server 2012 RC2 host, compiled with Visual Studio {2008, 2010,
2012, 2013} {x86, {x64}
passes ctest(s)
15 matches
Mail list logo