Is this change allowing clients to skip the SASL layer when connecting
to servers that have enabled the SASL layer? If so, how is the new
default behaviour disabled?
The existing but unimplemented 'allowSkip' method previously intended
to enable such behaviour still doesn't do anything, so is ther
On 6 July 2015 at 16:51, Andrew Stitcher wrote:
> On Mon, 2015-07-06 at 11:30 -0400, Rafael Schloming wrote:
>> I wired in allowSkip in a very minimal way just to restore the ability to
>> force the old behaviour. It would be a fairly trivial to change the name of
>> course,
>
> I'm not sure if th
On 6 July 2015 at 16:48, Gordon Sim wrote:
> On 07/06/2015 04:08 PM, Rafael Schloming wrote:
>>
>> Any sort of missing class really should be a compile time exception, which
>> I think means you must have stale class files *somewhere*. You could try
>> doing a find checkout -name "*.class" just as
On 6 July 2015 at 18:24, aconway wrote:
> On Mon, 2015-07-06 at 17:31 +0100, Gordon Sim wrote:
>> On 07/06/2015 05:22 PM, aconway wrote:
>> > On Mon, 2015-07-06 at 16:48 +0100, Gordon Sim wrote:
>> > > On 07/06/2015 04:08 PM, Rafael Schloming wrote:
>> > > > Any sort of missing class really should
On 6 July 2015 at 18:14, Andrew Stitcher wrote:
> On Mon, 2015-07-06 at 17:48 +0100, Robbie Gemmell wrote:
>> ...
>> The old toggle only used to define whether sasl was required or not
>> (which it historically was once you enabled the sasl layer, and the
>> toggle was
On 6 July 2015 at 18:28, Andrew Stitcher wrote:
> On Mon, 2015-07-06 at 13:14 -0400, Andrew Stitcher wrote:
>> On Mon, 2015-07-06 at 17:48 +0100, Robbie Gemmell wrote:
>> > ...
>> > The old toggle only used to define whether sasl was required or not
>> >
ther code that
uses them, which can do anything it likes) are now wrong as a result
of this latest change ;)
>
> On Mon, Jul 6, 2015 at 10:28 AM, Andrew Stitcher
> wrote:
>
>> On Mon, 2015-07-06 at 13:14 -0400, Andrew Stitcher wrote:
>> > On Mon, 2015-07-06 at 17:48 +0100,
I'd like to see something in the release to do with the session
outgoing-window problems that mean the new JMS client can't currently
send to ServiceBus.
As mentioend elsewhere earlier, a very basic change that leaves the
current default behaviour as it stands but would enable me to
configure the
I added https://issues.apache.org/jira/browse/PROTON-935 as a blocker.
We need to either drop Java 6 or fix compilation.
I also added https://issues.apache.org/jira/browse/PROTON-936 for the
session outgoing window stuff, with some initial changes for
discussion on https://github.com/apache/qpid-p
viour if the new setter was used is still at
https://github.com/gemmellr/qpid-proton/commit/b2b15a617b42bd36eacf9b51fb146223ba516496
though that might get garbase collected at some point as I rebased the
repo and orphaned it)
>
> On Fri, Jul 3, 2015 at 8:57 AM, Robbie Gemmell
> wrote:
>
>&
On 8 July 2015 at 10:03, Gordon Sim wrote:
> On 07/08/2015 02:22 AM, Rafael Schloming wrote:
>>
>> a value of zero is actually what
>> signals that the receiver needs to take some action here, and arguably an
>> initial value of zero is correct since it is signaling that the receiver
>> needs to t
o the latter given that noone except the CI box seems to be
testing it, Java 7 is already EOL itself, and most if not all of the
dependent proejcts that I am aware of using proton-j already require
Java 7 themselves now.
Robbie
On 24 September 2014 at 15:24, Robbie Gemmell wrote:
> The compilation
On 8 July 2015 at 15:49, Rafael Schloming wrote:
> On Wed, Jul 8, 2015 at 2:03 AM, Gordon Sim wrote:
>
>> On 07/08/2015 02:22 AM, Rafael Schloming wrote:
>>
>>> a value of zero is actually what
>>> signals that the receiver needs to take some action here, and arguably an
>>> initial value of zero
On 8 July 2015 at 16:03, Rafael Schloming wrote:
> On Wed, Jul 8, 2015 at 2:38 AM, Robbie Gemmell
> wrote:
>
>> On 8 July 2015 at 10:03, Gordon Sim wrote:
>> > On 07/08/2015 02:22 AM, Rafael Schloming wrote:
>> >>
>> >> a value of zero is actual
Hi Bozzo, some comments and questions.
I am seeing test failures due to NPE's from the new code:
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-j/1043/
There should be null checks on the remote Source and Target before
trying to copy them, since there are cases where they are allowe
On 8 July 2015 at 15:48, Ken Giusti wrote:
>
> Devs,
>
> As you probably know, I've pushed changes to the proton python bindings that
> make proton compatible with python3.
>
> Since then, I've hit bugs in the python3 stuff that could've been caught by
> running the above unit test on a linux sy
though due to issues in the
recent commit from Bozzo.
Robbie
On 8 July 2015 at 16:10, Timothy Bish wrote:
> +1 for dropping Java 6 from future releases.
>
> On 07/08/2015 09:59 AM, Robbie Gemmell wrote:
>> Epic bump.
>>
>> As per https://issues.apache.org/jira/bro
On 8 July 2015 at 17:59, Rafael Schloming wrote:
> On Wed, Jul 8, 2015 at 8:29 AM, Robbie Gemmell
> wrote:
>
>> The wording of "This identifies a current maximum outgoing transfer-id
>> that can be computed by subtracting one from the sum of
>> outgoing-wi
On 8 July 2015 at 20:13, Rob Godfrey wrote:
> As far as I can recall/reconstruct the only utility given by the
> outgoing window was so that the sender (of transfer frames) can
> indicate to the receiver (of transfer frames) that it will require
> notification of which frames have been seen by the
test_schedule_cancel
now = self.reactor.mark()
File
"/home/gemmellr/workspace/proton/tests/../proton-c/bindings/python/proton/reactor.py",
line 118, in mark
return pn_reactor_mark(self._impl)
NameError: global name 'pn_reactor_mark' is not defined
Robbie
On 8 J
Hi Bozzo,
This change also seems to be causing test failures when using the
maven build (if you update things to get past the earlier failures,
caused by the commit mentioned in the other thread on proton@):
proton_tests.reactor.ExceptionTest.test_schedule_cancel . fail
Error duri
#x27;ll test on a clean checkout next time. Sorry for all the mess.
> I've commited the missing methods to proton-j
>
> Bozzo
>
> On 9. 07. 15 12.14, Robbie Gemmell wrote:
>> Hi Bozzo,
>>
>> This change also seems to be causing test failures when using the
>&
Sending to the list...
-- Forwarded message --
From: Robbie Gemmell
Date: 9 July 2015 at 12:35
Subject: Re: [1/2] qpid-proton git commit: PROTON-937:
LinkImpl.localOpen() does not initialize source and target
To: Bozo Dragojevic
On 9 July 2015 at 12:23, Bozo Dragojevic wrote
d point, I'll see what I can do on that front.
>>
>>
>> - Original Message -
>>> From: "Robbie Gemmell"
>>> To: proton@qpid.apache.org
>>> Sent: Wednesday, July 8, 2015 12:21:57 PM
>>> Subject: Re: Proton Devs using Linux:
ad pip/tox installed, the tests would
> only run under python2 anyways.
>
>
> -K
>
> - Original Message -
>> From: "Robbie Gemmell"
>> To: proton@qpid.apache.org
>> Sent: Thursday, July 9, 2015 9:45:10 AM
>> Subject: Re: Proton Devs using Lin
I don't really know much about Go, so I mainly have questions rather
than answers.
- What would actually be included in this 'qpid-proton-go' repo vs the
existing qpid-proton repo?
- Have you looked into how other Apache projects are supporting "go
get", if there are any, to see what do they do?
On 13 July 2015 at 16:23, aconway wrote:
> On Mon, 2015-07-13 at 13:03 +0100, Robbie Gemmell wrote:
>> I don't really know much about Go, so I mainly have questions rather
>> than answers.
>>
>> - What would actually be included in this 'qpid-proton-go' r
On 13 July 2015 at 19:04, aconway wrote:
> On Mon, 2015-07-13 at 18:28 +0100, Robbie Gemmell wrote:
>> On 13 July 2015 at 16:23, aconway wrote:
>> > On Mon, 2015-07-13 at 13:03 +0100, Robbie Gemmell wrote:
>> > > I don't really know much about Go, so I
Hi folks,
There are a bunch of unresolved JIRAs assigned with the 0.9 fix-for
(http://s.apache.org/VnH). I resolved or updated a few that were
obviously complete or not started in 0.9, but there are 17 remaining
that need attention from folks involved with the JIRA or who know
something about the
The are currently 11 unresolved JIRAs assigned a 0.10 fix-for:
http://s.apache.org/ytK
Of those, 4 are listed as blockers:
https://issues.apache.org/jira/browse/PROTON-905
Long-lived connections leak sessions and links
https://issues.apache.org/jira/browse/PROTON-923
[SASL] PN_TRANSPORT_ERROR ev
Hi Alex,
It is the wrong directory name inside the tar file. The 'rc1' bits
were voted as the final 0.9.1 release.
There was an issue (since corrected) with some release scripting
changes made just before the release, and the dirname issue wasn't
noticed until after everything was finished and di
ROTON-905, as well as hopefully answer a few related questions on the list.
>
> --Rafael
>
> On Fri, Jul 17, 2015 at 3:35 AM, Robbie Gemmell
> wrote:
>
>> The are currently 11 unresolved JIRAs assigned a 0.10 fix-for:
>> http://s.apache.org/ytK
>>
>> Of those,
Looking nice, good job :)
(same goes to Gordon as well for the inspiring material :p)
Robbie
On 14 July 2015 at 23:31, aconway wrote:
> C++ tutorial is mostly done, if that interests you
> http://people.apache.org/~aconway/proton/
> or check out cjansen-cpp-client.
On 17 July 2015 at 23:32, Gordon Sim wrote:
> On 07/17/2015 10:04 PM, Rafael Schloming wrote:
>>
>> On Fri, Jul 17, 2015 at 12:47 PM, Gordon Sim wrote:
>>
>>> On 07/17/2015 08:15 PM, Rafael Schloming wrote:
>>>
On Fri, Jul 17, 2015 at 11:56 AM, Gordon Sim wrote:
On 07/17/2015 07
I think it would be good to do a beta for 0.10, given the alpha has
been out a couple weeks and had various issues on the proton-j side.
There are a couple of remaining blockers still needing resolved, but
it would be good to keep the process moving forwards and aid the
likleyhood of getting a rele
st them. ;-)
>
> --Rafael
>
> On Tue, Jul 21, 2015 at 8:42 AM, Robbie Gemmell
> wrote:
>
>> I think it would be good to do a beta for 0.10, given the alpha has
>> been out a couple weeks and had various issues on the proton-j side.
>> There are a couple of remain
I gave it a kick of the tyres as follows and all seemed well:
# Verified checksums
# Checked LICENCE and NOTICE present and look ok.
# Ran the build and tests via Maven
# Ran the build/tests/install via CMake
# Built qpid-cpp master against the above, ran the broker and
hello_world client example.
Hi folks,
I wanted to draw attention of some proton-c literate folks to look at
https://issues.apache.org/jira/browse/QPID-6651 as so far the issue
looks like it could be on the proton-c side.
This was raised during a discussion on the qpid-users list:
http://mail-archives.apache.org/mod_mbox/qpi
Hi Alex,
As mentioned previously off-list, the detach(closed=false) support in
proton was largely tacked on after the fact so there may still be some
issues there, but the only one I knew of that would play into what you
saw was that not free'ing a link object might lead to the situation.
I took
I think it would be good to do a second(/final) beta for 0.10 and keep
the process moving, hopefully then being able to spin an RC early next
week.
One of the previous blockers has been reverted and bumped to 0.11 due
to various issues with the earlier change. The other has had some work
done for
gt; New Feature PROTON-855
>> Add axTLS (embedded SSL) support to proton-c
>>
>> New Feature PROTON-852
>> Implement pn_getaddrinfo,pn_getprotobyname for platforms that not support
>> getaddrinfo(),getprotobyname()
>>
>>
>> - O
Hi all,
I have just made a 0.10.x branch, we will complete the 0.10 release
from there (more on that soon).
Robbie
Hi folks,
I have put up a 0.10 beta2 cut from the new 0.10.x branch. I'll be
looking to cut RC1 in the next couple of days and immediately proceed
to vote on it, so please give the beta a kick of the tyres and report
back your findings.
You can find the files here:
https://dist.apache.org/repos/d
On 4 August 2015 at 16:02, Andrew Stitcher wrote:
> On Mon, 2015-08-03 at 18:40 +0100, Robbie Gemmell wrote:
>> Hi folks,
>>
>> I have put up a 0.10 beta2 cut from the new 0.10.x branch. I'll be
>> looking to cut RC1 in the next couple of days and immediately pro
To be more explicit, master is now for 0.11 and I updated the versions
earlier to that end.
On 3 August 2015 at 17:04, Robbie Gemmell wrote:
> Hi all,
>
> I have just made a 0.10.x branch, we will complete the 0.10 release
> from there (more on that soon).
>
> Robbie
On 3 August 2015 at 18:40, Robbie Gemmell wrote:
> Hi folks,
>
> I have put up a 0.10 beta2 cut from the new 0.10.x branch. I'll be
> looking to cut RC1 in the next couple of days and immediately proceed
> to vote on it, so please give the beta a kick of the tyres and report
On 4 August 2015 at 17:30, Robbie Gemmell wrote:
> On 3 August 2015 at 18:40, Robbie Gemmell wrote:
>> Hi folks,
>>
>> I have put up a 0.10 beta2 cut from the new 0.10.x branch. I'll be
>> looking to cut RC1 in the next couple of days and immediately proceed
>
Hi all,
I have put up an RC for 0.10, please test it and vote accordingly.
The release archive and sig/checksums can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc1/
Maven artifacts for the Java bits can be found in a temporary staging repo at:
https://repository.apa
ypted.
>
> see https://issues.apache.org/jira/browse/PROTON-975
>
>
> - Original Message -
>> From: "Robbie Gemmell"
>> To: proton@qpid.apache.org, us...@qpid.apache.org
>> Sent: Wednesday, August 5, 2015 12:53:15 PM
>> Subject: [VOTE] Release Qpid Proton
ick 0.10.1 with that and any
other appropriate fixes in it.
Robbie
On 6 August 2015 at 10:13, Robbie Gemmell wrote:
> (Apologies for the duplicate mail to users@, just restoring proton@ to
> recipients)
>
> Ok :(
>
> Can other folks please still test this RC out for their use
een to progress and get a release out.
>> I'm thinking that I will spin RC2 on Monday, and if the SASL fix
>> doesnt make it we can turn around a quick 0.10.1 with that and any
>> other appropriate fixes in it.
>>
>> Robbie
>>
>> On 6 August 2015 at 10:1
Just to make it explicit, this vote on the first RC for Proton 0.10
was cancelled following discovery of a blocking bug in the form of a
crash in proton-c.
Robbie
Hi all,
I have put up a second cut for 0.10, please test it and vote accordingly.
This fixes a crash (PROTON-976) reported against the previous spin,
and adds a known issue (PROTON-975) of possible failure using the
DIGEST-MD5 mechanism against non-proton servers.
The release archive and sig/che
On 10 August 2015 at 19:34, Robbie Gemmell wrote:
> Hi all,
>
> I have put up a second cut for 0.10, please test it and vote accordingly.
>
> This fixes a crash (PROTON-976) reported against the previous spin,
> and adds a known issue (PROTON-975) of possible failure usin
I am cancelling the vote on the seconr RC for Proton 0.10, and will
shortly be preparing a third RC.
The changes in RC2 uncovered a issue, that while present previously
was not causing an observable problem before hand but now does
following the additional validation included in RC2 and this needs
Hi all,
I have put up a third cut for 0.10, please test it and vote accordingly.
Since RC2 there have been fixes for PROTON-978, PROTON-975, and PROTON-899.
The release archive and sig/checksums can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc3/
Maven artifacts fo
+1
I performed some of my earlier testing of RC2 using Qpid C++ 0.34,
ActiveMQ 5.12, and Qpid JMS master. I also verified that I was now
able to connect to qpidd using DIGEST-MD5 following the fix for
PROTON-975.
Robbie
On 11 August 2015 at 21:08, Robbie Gemmell wrote:
> Hi all,
>
> I
es yet.
>
> Not sure if FreeBSD is important enough to care too much, but it should
> work.
>
> [so no -1 yet, but investigating. IMO the FreeBSD failures aren't
> enough to reject the release, but the Ubuntu failures might be]
>
> Andrew
>
> On Tue, 2015-08-11 at
inux
> kernel (using Docker). All of the tests, including the SSL tests pass.
>
> -Ted
>
>
> On 08/13/2015 09:56 AM, Robbie Gemmell wrote:
>>
>> I have run up a fresh Ubuntu 14.04.3 install didn't see any issues
>> (once I figured out what packages to insta
se of uninitialised value of size 8
>>
>> Which seems like valgrind detected use of an uninitialised value.
>> I don't know it this is in proton or one of the lib it uses yet.
>>
>> Not sure if FreeBSD is important enough to care too much, but it
>> should
&
There were 7 binding and 1 non-binding +1 votes, with no other votes
received. The vote has passed.
I will re-tag the 0.10-rc3 tag in the repo as 0.10 proper, add the
release files to the dist release svn repo, and release the maven
staging repo. The website will be updated later after the artifac
I have added the 'input' files for the 0.10 release website update. I
havent yet published the output as the mirrors need a little more
time, but I'll do it either late tonight (UK) or at some point
tomorrow.
If you have any release notes additions (or anything else really) you
can make them now,
The Apache Qpid community is pleased to announce the immediate
availability of Apache Qpid Proton 0.10.
Qpid Proton is an AMQP 1.0 messaging library. It can be used in a wide
range of messaging applications including brokers, clients, routers,
bridges, proxies, and more.
This release incorporates
On 17 August 2015 at 21:11, Flavio Percoco wrote:
>
> Outsider question:
>
> Is there a reason why 0.10 is used rather than 0.10.0?
>
I mainly used 0.10 because it was versioned 0.10-SNAPSHOT beforehand
and had already gone through initial alpha/betas as 0.10 before I
started progressing things,
On 18 August 2015 at 07:48, Flavio Percoco wrote:
> On 17/08/15 21:57 +0100, Robbie Gemmell wrote:
>>
>> On 17 August 2015 at 21:11, Flavio Percoco wrote:
>
> [snip]
>>>
>>> Is that something we can change in qpid-proton ?
>>>
>>
>> I&#
I can see certain benefits to such a separation, mainly for folks
interested only in the bindings, but if I'm honest I'm not sure those
outweigh the additional complication it seems it may bring in some of
the other areas.
The python bindings are slightly more interesting than the others due
to be
Yes, its tagged as 0.10.
You may need to fetch the tags explicitly to see it: git fetch --tags
Robbie
On 19 August 2015 at 17:04, Irina Boverman wrote:
> Hi Robbie,
> Is there a tag/branch for proton java 0.10 released?
> Regards, Irina.
> - Original Message -----
> From:
Seems to be working here, and passed in CI on all the runs from
commits yesterday:
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-j/
NoSuchMethodError is an interesting one. I think code in that area
will have changed with Bozo's recent commit, but the only likely way
that should cau
On 19 August 2015 at 13:05, Flavio Percoco wrote:
> On 19/08/15 12:34 +0100, Robbie Gemmell wrote:
>>
>> I can see certain benefits to such a separation, mainly for folks
>> interested only in the bindings, but if I'm honest I'm not sure those
>> outweigh th
; Is there any special reason to limit the data size to 32767 nodes?
> It is sad that I have to proceed to use patched version for our systems.
>
> Best regards,
>
> 17.08.2015 23:57, Robbie Gemmell пишет:
>> On 17 August 2015 at 21:11, Flavio Percoco wrote:
>>
>>>
-clean to clear up my
checkout and repeated things, and they passed.
Robbie
On 19 August 2015 at 17:38, Robbie Gemmell wrote:
> Seems to be working here, and passed in CI on all the runs from
> commits yesterday:
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid
java tests, since it doesnt
explicitly build or clean the java bits using maven anywhere else:
http://git-wip-us.apache.org/repos/asf/qpid-proton/diff/daec4da4
On 27 August 2015 at 10:30, Robbie Gemmell wrote:
> Ok, there is definitely something odd going on.
>
> I noticed that the CI j
Hi folks,
Flavio raised the question on the 0.10 vote thread of whether we could
change our versions to always use 3 parts, rather than change back and
forth from 2 whenever there is a point release. I think this is a good
idea (I'm using 3 on the JMS client for the reasons he stated), so I'd
like
On 4 September 2015 at 20:26, Robbie Gemmell wrote:
> Hi folks,
>
> Flavio raised the question on the 0.10 vote thread of whether we could
> change our versions to always use 3 parts, rather than change back and
> forth from 2 whenever there is a point release. I think this is a g
I overlooked that your message had already ben moderated through when
I replied off-list earlier. Just so the answer is out there for anyone
else reading:
You self-manage subscriptions to the mailing lists, details are at:
http://qpid.apache.org/discussion.html
Robbie
On 28 October 2015 at 21:26
I see an error, as does Travis CI (both shown below), when running
make after this change. The Appveyor build is failing too (less clear
if its the same reason), though the build did complete on the ASF
Jenkins. After a quick google, the posts at
http://stackoverflow.com/questions/14431776/c-ntohs-
Otavio suggested the same change on the JIRA so I just went ahead and
made it. If there is a better change then someone with more of a clue
can still make it ;)
Robbie
On 3 November 2015 at 12:43, Robbie Gemmell wrote:
> I see an error, as does Travis CI (both shown below), when running
>
On 28 October 2015 at 10:49, Justin Ross wrote:
> Hi, everyone. The beta is now available from the following URL:
>
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-beta/
>
> Maven staging repo:
>
> https://repository.apache.org/content/repositories/orgapacheqpid-1047
>
> Test outp
On 4 November 2015 at 03:15, Justin Ross wrote:
> Hi, all. The RC is now available here:
>
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-rc/
>
> Maven staging repo:
>
> https://repository.apache.org/content/repositories/orgapacheqpid-1048/
>
> I will be away from my keyboard for
Hi Vladimir,
As per https://issues.apache.org/jira/browse/PROTON-754, Proton does
not currently expose the properties of the flow frame and so it isnt
possible to do transactional acquisition using it (or correctly handle
it not being supported). All the clients/brokers I am aware of
currently [us
On 9 November 2015 at 17:09, aconway wrote:
> On Mon, 2015-11-09 at 13:49 +, Marinov, Vladimir wrote:
>> Hello all,
>>
>> We are implementing AMQP support in our messaging server and for that
>> purpose we use Proton-j 0.9.1. I'm currently trying to implement
>> transactional acquisition and I
I would like to request
https://issues.apache.org/jira/browse/PROTON-1042 for inclusion in
0.11.0. More details on the JIRA.
Robbie
On 9 November 2015 at 18:26, Justin Ross wrote:
> Okay, I don't object to a respin to pick this up. If anyone else does,
> speak up. Alan, please line up a review
On 11 November 2015 at 12:53, Justin Ross wrote:
> The artifacts proposed for release are here:
>
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-rc2/
>
> Please indicate your vote below. If you favor releasing the 0.11.0 RC 2
> bits as 0.11.0 GA, vote +1. If you have reason to t
On 27 November 2015 at 16:06, Chefo wrote:
> Hi folks,
>
> I've been digging through the proton code for a couple days, looking for a
> way to initiate a TLS session upgrade as defined in section 5.2 of the AMQP
> 1.0 spec (
> http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-security-v1.0-os
On 4 December 2015 at 19:56, Philippe Le Rohellec wrote:
> I'm using Proton to receive messages from an Azure Service Bus queue.
> The receiver keeps a lock on each message it receives for a predefined
> amount of time, which I think matches the "Lock Duration" set on the queue
> on the Azure side
Hi all,
I have put up an RC for 0.11.1, please test it and vote accordingly.
The release archive and sig/checksums can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.1-rc1/
Maven artifacts for the Java bits can be found in a temporary staging repo at:
https://repository
On 15 December 2015 at 19:32, Robbie Gemmell wrote:
> Hi all,
>
> I have put up an RC for 0.11.1, please test it and vote accordingly.
>
> The release archive and sig/checksums can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.1-rc1/
>
> Mave
There were 4 binding +1 votes, and no other votes received. The vote has passed.
I will add the archives to the dist release repo, release the maven
staging repo, and create the final tag shortly. The website will be
updated later after the artifacts have had time to sync to the mirrors
and maven
Can I suggest a more basic change of simply removing the release
version from the Appveyor job id?
None of the other CI jobs have that, and given it has been wrong for
around 5 months it doesn't seem particularly noted by most folks. The
branch name could still be there as it is now, which in many
On 19 January 2016 at 15:25, Andrew Stitcher wrote:
> On Tue, 2016-01-19 at 10:39 +0000, Robbie Gemmell wrote:
>> Can I suggest a more basic change of simply removing the release
>> version from the Appveyor job id?
>>
>> None of the other CI jobs have that, and
On 19 January 2016 at 15:15, tourili wrote:
> Any hint from some experimented with this topic PLEASE
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/Android-client-ServiceBus-tp7636619p7636821.html
> Sent from the Apache Qpid Proton mailing list archive at Nabble.co
Fear not Sreeram, the change will be included in 0.12.
The 0.12 alpha was cut from master mainly to serve as a heads up the
release process is going to get under way, and help tease out any
obvious issues before a 0.12.x branch is created to progress the
release via a beta and any subsequent fixup
On 24 January 2016 at 07:19, wrote:
> PROTON-1062: c++: proton::connection_engine with client and server examples.
>
> Easier to use proton::connction_engine:
> - inherit and override io_read, io_write, io_close to provide IO
> functionality.
> - processing logic (read/write/dispatch) built into
Hi Justin,
I see you have created the 0.12.x branch, but before you actually spin
the beta, could I request the following...
The latest commit on https://issues.apache.org/jira/browse/PROTON-1100
didnt make the branch.
https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=6422e24
Also sinc
Great, thanks Justin. Both changes are now picked onto the 0.12.x branch.
Robbie
On 26 January 2016 at 14:16, Justin Ross wrote:
> Thanks, Robbie. Both are approved.
>
>
> On Tue, Jan 26, 2016 at 6:10 AM, Robbie Gemmell
> wrote:
>
>> Hi Justin,
>>
>> I se
Hi Justin,
I'd like to request the following for inclusion in 0.12.0:
Stop the proton-j transport from erroneously emitting various frame
types after a Close was sent.
https://issues.apache.org/jira/browse/PROTON-1114
https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=bcd08cc
Some minor
On 27 January 2016 at 21:09, Andrew Stitcher wrote:
> This [1] is really an interop bug, but I suspect it will be annoying to
> anyone using earlier versions of ActiveMQ.
>
> The fix is pretty small and seems low risk to me.
>
> Andrew
>
> [1] https://issues.apache.org/jira/browse/PROTON-1055
I g
On 27 January 2016 at 00:51, Justin Ross wrote:
> Hi, folks. The beta is now available from the following URL:
>
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.0-beta/
>
> Maven staging repo:
>
> https://repository.apache.org/content/repositories/orgapacheqpid-1059
>
> Test out
On 29 January 2016 at 07:01, Clemens Vasters wrote:
> It appears that Proton-J doesn't implement the WebSocket protocol binding,
> yet. (I may also not be looking in the right places)
>
> Is that on the backlog for some time in the nearer future?
>
> Thank you
> Clemens
>
Hi Clemens
I'm not awa
Stitcher
> wrote:
>
>> I've approved both of these for inclusion (in the JIRAs).
>>
>> Andrew
>>
>> On Thu, 2016-01-28 at 11:04 +, Robbie Gemmell wrote:
>> > Hi Justin,
>> >
>> > I'd like to request the following for in
101 - 200 of 728 matches
Mail list logo
