Looks like MOVED issue has been resolved (ZOOKEEPER-710). I'm planning
to publish a 3.3.0 release candidate tomorrow.
Patrick
Patrick Hunt wrote:
Another update. 121 has been resolved, all of the remaining patches have
been applied and non-blockers moved out of 3.3.0.
A new issue has recentl
Another update. 121 has been resolved, all of the remaining patches have
been applied and non-blockers moved out of 3.3.0.
A new issue has recently been identified (see SESSION MOVED thread on
the user list). One user is reporting "session moved" errors in 3.2.2
when there shouldn't be. No jir
The release candidate has been blocked by ZOOKEEPER-121. We're working
to address, it's been failing intermittently on hudson. Additionally
Hudson itself has been very unstable, Mahadev and I have been working to
address this as well but that's slowing us considerably. Once the
blockers are dea
I was planning to cut a release candidate today, however there are a few
blockers outstanding for this release that we need to address before I
can do so. We're in the final stretch though.
There are a number of open issues still pending for 3.3.0, however most
of these are non-blockers and I'
March 10 is rapidly approaching. There aren't any blockers left, my plan
is to commit any reviewed "patch availables" and push any remaining
non-blockers into 3.4.0 on Weds as part of cutting the 3.3.0 release
candidate. If you have something that you want to get into 3.3.0 you
need to get the
Just a reminder, 3.3.0 is coming up fast. I will re-triage the JIRA list
sometime next week with an eye towards reducing the list of "fix for
3.3.0", pushing non-critical, non-resourced issues to the 3.4.0 release.
So if you have something you want to get into 3.3.0 that's a non-blocker
please
