RESULT VOTE: Release Proton 0.8 RC5 as 0.8 final
The vote carries unanimously with 5 (binding) and 2 (non-binding) +1's. I've created the branch/tag and checked in the artifacts to the dist repo. I will update the web site and send out an announcement tomorrow after the release has propagated to all the mirrors. --Rafael On Mon, Oct 27, 2014 at 9:51 PM, Rafael Schloming r...@alum.mit.edu 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. I've posted RC5 in the usual places. The only difference from RC4 is a one line delta that replaces the assertion failure when we receive out-of-sequence ids with a connection shutdown error. Please have a look and register your vote. Source code can be found here: http://people.apache.org/~rhs/qpid-proton-0.8rc5/ Java binaries are here: https://repository.apache.org/content/repositories/orgapacheqpid-1021 [ ] Yes, release Proton 0.8 RC5 as 0.8 final [ ] No, because ... --Rafael
[VOTE]: migrate the proton repo to use git
Hi Everyone, I'm planning on updating the release script for 0.9 to automate the last few details of the release process and to do proper branching. Given that the release script must make use of the canonical repo to work properly, it occurs to me that if we're going to switch over to git then now would be a good time so that I only need to update the release script once. I'd therefore like to call for a formal vote to approve the switch. [ ] Yes, migrate the proton repo over to git. [ ] No, keep it in svn. --Rafael
Re: [VOTE]: migrate the proton repo to use git
[ X ] Yes, migrate the proton repo over to git. On 30 October 2014 10:59, Rafael Schloming r...@alum.mit.edu wrote: Hi Everyone, I'm planning on updating the release script for 0.9 to automate the last few details of the release process and to do proper branching. Given that the release script must make use of the canonical repo to work properly, it occurs to me that if we're going to switch over to git then now would be a good time so that I only need to update the release script once. I'd therefore like to call for a formal vote to approve the switch. [ ] Yes, migrate the proton repo over to git. [ ] No, keep it in svn. --Rafael
Re: [VOTE]: migrate the proton repo to use git
[ X] Yes, migrate the proton repo over to git.
Re: [VOTE]: migrate the proton repo to use git
[ X ] Yes, migrate the proton repo over to git. On 10/30/2014 06:59 AM, Rafael Schloming wrote: Hi Everyone, I'm planning on updating the release script for 0.9 to automate the last few details of the release process and to do proper branching. Given that the release script must make use of the canonical repo to work properly, it occurs to me that if we're going to switch over to git then now would be a good time so that I only need to update the release script once. I'd therefore like to call for a formal vote to approve the switch. [ ] Yes, migrate the proton repo over to git. [ ] No, keep it in svn. --Rafael -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: [VOTE]: migrate the proton repo to use git
[ X ] Yes, migrate the proton repo over to git.
[jira] [Commented] (PROTON-735) SASL authentication failures appear as I/O failures
[ https://issues.apache.org/jira/browse/PROTON-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190722#comment-14190722 ] Ken Giusti commented on PROTON-735: --- This seems related... I could be wrong. SASL authentication failures appear as I/O failures --- Key: PROTON-735 URL: https://issues.apache.org/jira/browse/PROTON-735 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.8 Reporter: Ken Giusti Fix For: 0.9 Using the current SASL api, an application has to poll the pn_sasl_t object's state (pn_sasl_state()) until a terminal state is reached (STATE_PASS/FAIL). Once the terminal state is reached, the outcome can be queried via pn_sasl_outcome. Unfortunately, when the sasl client receives an authentication failure outcome from the sasl server, the sasl layer returns PN_ERR from its input processing code. This causes the pn_transport_push() to return a generic error. From the application's point of view, this effectively results in the transport failing -before- the sasl terminal state has been reached. The application will interpret this event as a generic input failure on the transport - not the authentication failure it actually was. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-735) SASL authentication failures appear as I/O failures
[ https://issues.apache.org/jira/browse/PROTON-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-735: -- Description: Using the current SASL api, an application has to poll the pn_sasl_t object's state (pn_sasl_state()) until a terminal state is reached (STATE_PASS/FAIL). Once the terminal state is reached, the outcome can be queried via pn_sasl_outcome. Unfortunately, when the sasl client receives an authentication failure outcome from the sasl server, the sasl layer returns PN_ERR from its input processing code. This causes the pn_transport_push() to return a generic error. From the application's point of view, this effectively results in the transport failing *before* the sasl terminal state has been reached. The application will interpret this event as a generic input failure on the transport - not the authentication failure it actually was. was: Using the current SASL api, an application has to poll the pn_sasl_t object's state (pn_sasl_state()) until a terminal state is reached (STATE_PASS/FAIL). Once the terminal state is reached, the outcome can be queried via pn_sasl_outcome. Unfortunately, when the sasl client receives an authentication failure outcome from the sasl server, the sasl layer returns PN_ERR from its input processing code. This causes the pn_transport_push() to return a generic error. From the application's point of view, this effectively results in the transport failing -before- the sasl terminal state has been reached. The application will interpret this event as a generic input failure on the transport - not the authentication failure it actually was. SASL authentication failures appear as I/O failures --- Key: PROTON-735 URL: https://issues.apache.org/jira/browse/PROTON-735 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.8 Reporter: Ken Giusti Fix For: 0.9 Using the current SASL api, an application has to poll the pn_sasl_t object's state (pn_sasl_state()) until a terminal state is reached (STATE_PASS/FAIL). Once the terminal state is reached, the outcome can be queried via pn_sasl_outcome. Unfortunately, when the sasl client receives an authentication failure outcome from the sasl server, the sasl layer returns PN_ERR from its input processing code. This causes the pn_transport_push() to return a generic error. From the application's point of view, this effectively results in the transport failing *before* the sasl terminal state has been reached. The application will interpret this event as a generic input failure on the transport - not the authentication failure it actually was. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
