[
https://issues.apache.org/jira/browse/ZOOKEEPER-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986863#action_12986863
]
Vishal K commented on ZOOKEEPER-880:
Mahadev,
I am not sure which review comments y
btw, I did a patch for 913 that was to be fixed in 3.3.3, but only got
applied to trunk due to a source conflict. I'll fix the conflict and
commit it to the 3.3 branch for inclusion in 3.3.3 asap.
Patrick
On Tue, Jan 25, 2011 at 12:03 PM, Patrick Hunt wrote:
> Our typical process is to have a ru
Our typical process is to have a running fix release in parallel with
the trunk. So 3.3.3 was created in jira after 3.3.2 went out, 3.4.0 is
trunk. This catches any new issues that might need a fix release
(3.3.3). We triage the issues marked for the fix release (3.3.3) and
also apply those changes
I would really like to see 962 fix released asap as well.
C
-Original Message-
From: Benjamin Reed [mailto:br...@yahoo-inc.com]
Sent: Tuesday, January 25, 2011 2:27 PM
To: dev@zookeeper.apache.org
Subject: 3.3.3 release
the 962 bug we fixed was pretty severe. i would like to get a relea
the 962 bug we fixed was pretty severe. i would like to get a release
out asap.
i was looking over the bugs tagged for 3.3.3 and almost all of them look
like the should really be for 3.4. in my opinion only severe bugs should
be back ported to previous releases, and most of the bugs marked 3.3
[
https://issues.apache.org/jira/browse/ZOOKEEPER-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal K updated ZOOKEEPER-932:
---
Attachment: ZOOKEEPER-932.patchv3
resubmitting with license
> Move blocking read/write calls to S
