There were 5 binding and 1 non-binding +1 votes, with no other votes received.
The vote has passed.
I am going to publish release artifacts into dist release repo and
maven repo. After that I will update web site.
Kind Regards,
Alex
--
This vote is now closed.
I will publish results in separate email.
Kind Regards,
Alex
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
+1
On 3 December 2015 at 15:06, Oleksandr Rudyy wrote:
> Hi folks,
>
> I would like to initiate new voting to release Qpid Java Components 6.0.0
> RC5 as the final 6.0.0.
>
> Maven release artifacts are available from maven staging repo at:
> https://repository.apache.org/content/repositories/org
+1
On 03/12/15 15:06, Oleksandr Rudyy wrote:
Hi folks,
I would like to initiate new voting to release Qpid Java Components 6.0.0
RC5 as the final 6.0.0.
Maven release artifacts are available from maven staging repo at:
https://repository.apache.org/content/repositories/orgapacheqpid-1056
Sou
On 3 December 2015 at 15:06, Oleksandr Rudyy wrote:
> Hi folks,
>
> I would like to initiate new voting to release Qpid Java Components 6.0.0
> RC5 as the final 6.0.0.
>
> Maven release artifacts are available from maven staging repo at:
> https://repository.apache.org/content/repositories/orgapac
On 12/03/2015 04:21 PM, Rob Godfrey wrote:
How did you "re-use"? did you start up RC5, stop, replace the config.json
and restart... or just try to start up rc5 with this config file (and this
alone) in the work directory?
I copied the file into the new work directory before starting rc5 for
th
I don't suppose you kept the broker logs?
How did you "re-use"? did you start up RC5, stop, replace the config.json
and restart... or just try to start up rc5 with this config file (and this
alone) in the work directory?
In the latter case I can see you might have had an issue if you didn't have
On 12/03/2015 03:06 PM, Oleksandr Rudyy wrote:
Hi folks,
I would like to initiate new voting to release Qpid Java Components 6.0.0
RC5 as the final 6.0.0.
Maven release artifacts are available from maven staging repo at:
https://repository.apache.org/content/repositories/orgapacheqpid-1056
Sou
On 12/03/2015 10:03 AM, Gordon Sim wrote:
On 12/02/2015 09:45 PM, Rob Godfrey wrote:
On 2 December 2015 at 21:45, Gordon Sim wrote:
From the proton python examples, I was unable to connect as that client
populates the hostname with a host and port combination, which was
causing
the broker to
+1 from me as well
(sent / received messages in 0-9-1, 0-10 and 1.0 using Java client. 0-10
and 1.0 using C++)
On 3 December 2015 at 15:20, Keith W wrote:
> +1 to making 6.0.0 RC5 GA
>
> On 3 December 2015 at 15:06, Oleksandr Rudyy wrote:
>
> > Hi folks,
> >
> > I would like to initiate new vo
+1 to making 6.0.0 RC5 GA
On 3 December 2015 at 15:06, Oleksandr Rudyy wrote:
> Hi folks,
>
> I would like to initiate new voting to release Qpid Java Components 6.0.0
> RC5 as the final 6.0.0.
>
> Maven release artifacts are available from maven staging repo at:
> https://repository.apache.org/
Hi folks,
I would like to initiate new voting to release Qpid Java Components 6.0.0
RC5 as the final 6.0.0.
Maven release artifacts are available from maven staging repo at:
https://repository.apache.org/content/repositories/orgapacheqpid-1056
Source and binary bundles are available from dev sta
Hi all,
I am canceling this voting as we decided to build RC5 to include fixes
for QPID-6926 and QPID-6928.
Thanks a lot for testing and reporting issues with the RC4.
Kind Regards,
Alex
On 3 December 2015 at 11:06, Rob Godfrey wrote:
> Does the broker put the full stack trace of the NullPoint
Does the broker put the full stack trace of the NullPointerException in its
logs?
I'll try to fix this (as well as the out of order detach) if I can locate
it.
Cheers,
Rob
On 3 December 2015 at 10:03, Gordon Sim wrote:
> On 12/02/2015 09:45 PM, Rob Godfrey wrote:
>
>> On 2 December 2015 at 21:
On 12/02/2015 03:22 PM, Oleksandr Rudyy wrote:
Thanks a lot for pointing out that source release bundle is not available
in staging repo. I created 6.0.0 RC4 source bundle and put it together with
binary bundles into dev area of the dist repo under:
https://dist.apache.org/repos/dist/dev/qpid/ja
On 12/02/2015 09:45 PM, Rob Godfrey wrote:
On 2 December 2015 at 21:45, Gordon Sim wrote:
From the proton python examples, I was unable to connect as that client
populates the hostname with a host and port combination, which was causing
the broker to close the connection:
[...]
In its defaul
On 2 December 2015 at 22:45, Rob Godfrey wrote:
>
>
> On 2 December 2015 at 21:45, Gordon Sim wrote:
>
>>
>>
[.. snip ..]
>
> In its default configuration the Java Broker will accept any valid
> hostname or IP address as the "hostname", or the empty string, or
> "default".
>
any valid hostnam
On 2 December 2015 at 21:45, Gordon Sim wrote:
> On 12/02/2015 03:22 PM, Oleksandr Rudyy wrote:
>
>> Robbie,
>>
>> Thanks a lot for pointing out that source release bundle is not available
>> in staging repo. I created 6.0.0 RC4 source bundle and put it together
>> with
>> binary bundles into dev
On 12/02/2015 08:45 PM, Gordon Sim wrote:
On 12/02/2015 03:22 PM, Oleksandr Rudyy wrote:
Robbie,
Thanks a lot for pointing out that source release bundle is not available
in staging repo. I created 6.0.0 RC4 source bundle and put it together
with
binary bundles into dev area of the dist repo un
On 12/02/2015 03:22 PM, Oleksandr Rudyy wrote:
Robbie,
Thanks a lot for pointing out that source release bundle is not available
in staging repo. I created 6.0.0 RC4 source bundle and put it together with
binary bundles into dev area of the dist repo under:
https://dist.apache.org/repos/dist/de
+1
On 2 December 2015 at 15:22, Oleksandr Rudyy wrote:
> Robbie,
>
> Thanks a lot for pointing out that source release bundle is not available
> in staging repo. I created 6.0.0 RC4 source bundle and put it together with
> binary bundles into dev area of the dist repo under:
>
> https://dist.apac
+1
On 2 December 2015 at 15:22, Oleksandr Rudyy wrote:
> Robbie,
>
> Thanks a lot for pointing out that source release bundle is not available
> in staging repo. I created 6.0.0 RC4 source bundle and put it together with
> binary bundles into dev area of the dist repo under:
>
> https://dist.apa
Robbie,
Thanks a lot for pointing out that source release bundle is not available
in staging repo. I created 6.0.0 RC4 source bundle and put it together with
binary bundles into dev area of the dist repo under:
https://dist.apache.org/repos/dist/dev/qpid/java/6.0.0-rc4/
Kind Regards,
Alex
On 2
On 2 December 2015 at 12:58, Robbie Gemmell wrote:
> On 2 December 2015 at 10:51, Oleksandr Rudyy wrote:
>> Hi all,
>>
>> I have produced 6.0.0 RC4 build and would like to initiate voting to
>> release Qpid Java Components 6.0.0 RC4 as the final 6.0.0.
>>
>> The release artifacts are available fr
On 2 December 2015 at 10:51, Oleksandr Rudyy wrote:
> Hi all,
>
> I have produced 6.0.0 RC4 build and would like to initiate voting to
> release Qpid Java Components 6.0.0 RC4 as the final 6.0.0.
>
> The release artifacts are available from maven staging repo at:
> https://repository.apache.org/co
Hi all,
I have produced 6.0.0 RC4 build and would like to initiate voting to
release Qpid Java Components 6.0.0 RC4 as the final 6.0.0.
The release artifacts are available from maven staging repo at:
https://repository.apache.org/content/repositories/orgapacheqpid-1055
If you want to test it out
26 matches
Mail list logo
