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
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
[ 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
[ X] Yes, migrate the proton repo over to 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
[ X ] Yes, migrate the proton repo over to git.
[
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
[
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
