[RESULT] [VOTE] Release RC3 as Qpid 0.8
As the 3 required +1 votes were gained, the vote has passed. RC3 is now officially Qpid 0.8. The final tally of votes was as follows: - There were 9 +1 votes by committers, 4 of which are PMC members. - There were no -1 votes. - There was 1 'undecided'(0?) vote due to an apparent cluster test issue, which was responded to as being an issue with test itself that is fixed on trunk, however the original vote wasn't updated and so stands. I have copied the files to the distribution area, and they are now live at: http://www.apache.org/dist/qpid I will work on updating the website tomorrow, giving the mirrors time to update in the meantime. I will also put out a draft for the announcement email which will be sent early next week. Robbie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: [RESULT] [VOTE] Release RC3 as Qpid 0.8
Great news! Thanks very much for ushering 0.8 through the release process, Robbie! You did a really nice job - well done. -Steve -Original Message- From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com] Sent: Saturday, December 04, 2010 11:01 AM To: dev@qpid.apache.org Subject: [RESULT] [VOTE] Release RC3 as Qpid 0.8 As the 3 required +1 votes were gained, the vote has passed. RC3 is now officially Qpid 0.8. The final tally of votes was as follows: - There were 9 +1 votes by committers, 4 of which are PMC members. - There were no -1 votes. - There was 1 'undecided'(0?) vote due to an apparent cluster test issue, which was responded to as being an issue with test itself that is fixed on trunk, however the original vote wasn't updated and so stands. I have copied the files to the distribution area, and they are now live at: http://www.apache.org/dist/qpid I will work on updating the website tomorrow, giving the mirrors time to update in the meantime. I will also put out a draft for the announcement email which will be sent early next week. Robbie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2968) Blocking on dead sockets
[ https://issues.apache.org/jira/browse/QPID-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2968: - Fix Version/s: (was: 0.8) (was: 0.7) Removed the Fix For versions 0.7 and 0.8, as the 0.8 release is now finalised. Blocking on dead sockets Key: QPID-2968 URL: https://issues.apache.org/jira/browse/QPID-2968 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: Future, 0.9, 0.8, 0.7 Environment: Does not matter Reporter: Dmitry Konishchev Fix For: Future, 0.9 Attachments: patch * If you open a few connections, and one of them breaks (for example, due to a network error), another connections can be locked for time, which is equal to network timeout of the broken connection. This happens due to working with sockets in blocking mode and due to using one Selector for all connections. * All connections could become locked forever due to races between Driver and Selector objects. Driver object removes itself from the Selector non-atomically and a situation when Driver is alredy closed, but the Selector refers to it could happen. In this case select() call in the Selector raise an exeption due to self._transport.fileno() call on Driver where self._transport is None. The selector doesn't handle errors on select(), so the selector's thread will be stopped due to unhandled Exception. * There is no checks on EINTR error on os.* calls. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
