You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by Alex O'Ree <al...@apache.org> on 2017/02/05 13:30:39 UTC
[VOTE] jUDDI-3.3.4 (fixed)
Sorry, the last email had the incorrect subject line!
Dear jUDDI enthusiasts,
The new release is here! This release is primarily bug fixes.
The release distribution is temporarily available here
https://www.dropbox.com/sh/bt7jes1jzl94qh1/AACh43p7QIfu5hyCb9gut6_Ka?dl=0
The release artifacts are staged in nexus:
https://repository.apache.org/content/repositories/orgapachejuddi-1009/
and we have a tag at:
https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.4
Small change set this time. 1 bug fix and the rest were pom updates.
Testing on non default tomcat/cxf/debry containers is appreciated.
Please give it a spin and cast your vote. This vote will be open for
the next 72 hours per the release policy, which is:
- the vote will be closed as soon as 6 hours have past and >7 +1
votes are received with no -1 vote being cast, or
- if after 12h >5 +1 votes have been cast with no -1 vote, or
- if after 24h if 3 +1 votes have been cast with no -1 vote, or failing that
- after 72h provided at least 3 +1 votes have been cast and there is
a majority of +1 votes from the cast votes.
+1
Bug
[JUDDI-967] - Suspicious incrementers in for loops
[JUDDI-968] - Update pom dependencies for vulnerable libraries
Re: [VOTE] jUDDI-3.3.4 (fixed)
Posted by Alex O'Ree <sp...@gmail.com>.
The vote passed. I'll finish up the release process shortly
On Sun, Feb 5, 2017 at 2:27 PM, Matthieu Ghilain <gh...@gmail.com> wrote:
> +1 from me as well if I have the right to vote ☺
>
> On Sun, 5 Feb 2017 20:26 Steve Viens, <sv...@gmail.com> wrote:
>
>> +1 from me as well.
>>
>> Steve Viens
>> sviens@gmail.com
>> 603-828-2397 <(603)%20828-2397>
>>
>> On Sun, Feb 5, 2017 at 10:24 AM, Kurt T Stam <ku...@gmail.com> wrote:
>>
>> +1 from me. --Kurt
>>
>> On 2/5/17 8:30 AM, Alex O'Ree wrote:
>>
>> Sorry, the last email had the incorrect subject line!
>>
>>
>> Dear jUDDI enthusiasts,
>>
>> The new release is here! This release is primarily bug fixes.
>>
>> The release distribution is temporarily available here
>> https://www.dropbox.com/sh/bt7jes1jzl94qh1/AACh43p7QIfu5hyCb9gut6_Ka?dl=0
>>
>> The release artifacts are staged in nexus:
>> https://repository.apache.org/content/repositories/orgapachejuddi-1009/
>>
>> and we have a tag at:
>> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.
>> git;a=tag;h=refs/tags/juddi-3.3.4
>>
>>
>> Small change set this time. 1 bug fix and the rest were pom updates.
>> Testing on non default tomcat/cxf/debry containers is appreciated.
>>
>>
>> Please give it a spin and cast your vote. This vote will be open for
>> the next 72 hours per the release policy, which is:
>> - the vote will be closed as soon as 6 hours have past and >7 +1
>> votes are received with no -1 vote being cast, or
>> - if after 12h >5 +1 votes have been cast with no -1 vote, or
>> - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
>> that
>> - after 72h provided at least 3 +1 votes have been cast and there is
>> a majority of +1 votes from the cast votes.
>>
>>
>> +1
>>
>> Bug
>>
>> [JUDDI-967] - Suspicious incrementers in for loops
>> [JUDDI-968] - Update pom dependencies for vulnerable libraries
>>
>>
>>
>>
>>
Re: [VOTE] jUDDI-3.3.4 (fixed)
Posted by Matthieu Ghilain <gh...@gmail.com>.
+1 from me as well if I have the right to vote ☺
On Sun, 5 Feb 2017 20:26 Steve Viens, <sv...@gmail.com> wrote:
> +1 from me as well.
>
> Steve Viens
> sviens@gmail.com
> 603-828-2397
>
> On Sun, Feb 5, 2017 at 10:24 AM, Kurt T Stam <ku...@gmail.com> wrote:
>
> +1 from me. --Kurt
>
> On 2/5/17 8:30 AM, Alex O'Ree wrote:
>
> Sorry, the last email had the incorrect subject line!
>
>
> Dear jUDDI enthusiasts,
>
> The new release is here! This release is primarily bug fixes.
>
> The release distribution is temporarily available here
> https://www.dropbox.com/sh/bt7jes1jzl94qh1/AACh43p7QIfu5hyCb9gut6_Ka?dl=0
>
> The release artifacts are staged in nexus:
> https://repository.apache.org/content/repositories/orgapachejuddi-1009/
>
> and we have a tag at:
>
> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.4
>
>
> Small change set this time. 1 bug fix and the rest were pom updates.
> Testing on non default tomcat/cxf/debry containers is appreciated.
>
>
> Please give it a spin and cast your vote. This vote will be open for
> the next 72 hours per the release policy, which is:
> - the vote will be closed as soon as 6 hours have past and >7 +1
> votes are received with no -1 vote being cast, or
> - if after 12h >5 +1 votes have been cast with no -1 vote, or
> - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
> that
> - after 72h provided at least 3 +1 votes have been cast and there is
> a majority of +1 votes from the cast votes.
>
>
> +1
>
> Bug
>
> [JUDDI-967] - Suspicious incrementers in for loops
> [JUDDI-968] - Update pom dependencies for vulnerable libraries
>
>
>
>
>
Re: [VOTE] jUDDI-3.3.4 (fixed)
Posted by Steve Viens <sv...@gmail.com>.
+1 from me as well.
Steve Viens
sviens@gmail.com
603-828-2397
On Sun, Feb 5, 2017 at 10:24 AM, Kurt T Stam <ku...@gmail.com> wrote:
> +1 from me. --Kurt
>
> On 2/5/17 8:30 AM, Alex O'Ree wrote:
>
>> Sorry, the last email had the incorrect subject line!
>>
>>
>> Dear jUDDI enthusiasts,
>>
>> The new release is here! This release is primarily bug fixes.
>>
>> The release distribution is temporarily available here
>> https://www.dropbox.com/sh/bt7jes1jzl94qh1/AACh43p7QIfu5hyCb9gut6_Ka?dl=0
>>
>> The release artifacts are staged in nexus:
>> https://repository.apache.org/content/repositories/orgapachejuddi-1009/
>>
>> and we have a tag at:
>> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.g
>> it;a=tag;h=refs/tags/juddi-3.3.4
>>
>>
>> Small change set this time. 1 bug fix and the rest were pom updates.
>> Testing on non default tomcat/cxf/debry containers is appreciated.
>>
>>
>> Please give it a spin and cast your vote. This vote will be open for
>> the next 72 hours per the release policy, which is:
>> - the vote will be closed as soon as 6 hours have past and >7 +1
>> votes are received with no -1 vote being cast, or
>> - if after 12h >5 +1 votes have been cast with no -1 vote, or
>> - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
>> that
>> - after 72h provided at least 3 +1 votes have been cast and there is
>> a majority of +1 votes from the cast votes.
>>
>>
>> +1
>>
>> Bug
>>
>> [JUDDI-967] - Suspicious incrementers in for loops
>> [JUDDI-968] - Update pom dependencies for vulnerable libraries
>>
>
>
>
Re: [VOTE] jUDDI-3.3.4 (fixed)
Posted by Kurt T Stam <ku...@gmail.com>.
+1 from me. --Kurt
On 2/5/17 8:30 AM, Alex O'Ree wrote:
> Sorry, the last email had the incorrect subject line!
>
>
> Dear jUDDI enthusiasts,
>
> The new release is here! This release is primarily bug fixes.
>
> The release distribution is temporarily available here
> https://www.dropbox.com/sh/bt7jes1jzl94qh1/AACh43p7QIfu5hyCb9gut6_Ka?dl=0
>
> The release artifacts are staged in nexus:
> https://repository.apache.org/content/repositories/orgapachejuddi-1009/
>
> and we have a tag at:
> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.4
>
>
> Small change set this time. 1 bug fix and the rest were pom updates.
> Testing on non default tomcat/cxf/debry containers is appreciated.
>
>
> Please give it a spin and cast your vote. This vote will be open for
> the next 72 hours per the release policy, which is:
> - the vote will be closed as soon as 6 hours have past and >7 +1
> votes are received with no -1 vote being cast, or
> - if after 12h >5 +1 votes have been cast with no -1 vote, or
> - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing that
> - after 72h provided at least 3 +1 votes have been cast and there is
> a majority of +1 votes from the cast votes.
>
>
> +1
>
> Bug
>
> [JUDDI-967] - Suspicious incrementers in for loops
> [JUDDI-968] - Update pom dependencies for vulnerable libraries