[ 
https://issues.apache.org/jira/browse/PROTON-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410094#comment-16410094
 ] 

Alan Conway commented on PROTON-1806:
-------------------------------------

You can build your own Gem from source and run it using the existing released C 
library - the ruby changes do not require a new C library. Use the following 
commands:
{code:java}
$ git clone https://git-wip-us.apache.org/repos/asf/qpid-proton.git
$ cd qpid-proton; mkdir build; cd build
$ cmake -DBUILD_BINDING=ruby .. && make ruby-gem
$ find -name *.gem
./proton-c/bindings/ruby/gem/qpid_proton-0.22.0.gem{code}
The "official" gem can only be released as part of the Apache release process 
which requires a vote etc. The release is due very soon now, but I'm 
reassigning this bug to [~justi9] who keeps track of the release schedule and 
can give a more authoritative answer.

> Release qpid_proton gem with heartbeating implemented
> -----------------------------------------------------
>
>                 Key: PROTON-1806
>                 URL: https://issues.apache.org/jira/browse/PROTON-1806
>             Project: Qpid Proton
>          Issue Type: Wish
>          Components: ruby-binding
>            Reporter: Miha Plesko
>            Assignee: Justin Ross
>            Priority: Major
>
> We use qpid_proton gem in RedHat CloudForms to capture events from ActiveMQ 
> queue. Recently we discovered a blocking bug in this gem which results in 
> client connection being disconnected every 2-3 minutes accompanied with file 
> descriptor leakage bug as described here:
> https://issues.apache.org/jira/browse/PROTON-1782 and
> https://issues.apache.org/jira/browse/PROTON-1791
> Both issues are fixed by now and merged qpid_proton master branch, many 
> thanks to [~aconway], [~astitcher], [~jdanek] for amazing response time.
>  
> I'm opening this ticket to discuss release plans for the qpid_proton gem. 
> CloudForms is about to be released first week in April and our initial plan 
> was to monkey-patch the gem to include those fixes. It turns our, however, 
> that changes modify gem's core to much to do the monkey-patching, hence we 
> decided to wait for you guys to perform the next release.
>  
> Q: Do you happen to know specific date when releasing new gem version is 
> supposed to happen? I remember we mentioned "within a couple of weeks" here 
> https://issues.apache.org/jira/browse/PROTON-1782?focusedCommentId=16401841&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16401841
>  , but we would need as good estimate as possible since we need to 
> communicate to customers how long they need to wait
>  
> Thanks for your great work, looking forward to be hearing from you!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to