[jira] [Updated] (CURATOR-397) Created strongly typed model DSL

[ https://issues.apache.org/jira/browse/CURATOR-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-397: - Fix Version/s: 4.0.0 > Created strongly typed model DSL > ---

[jira] [Resolved] (CURATOR-426) Prep Apache Curator 4.0.0

[ https://issues.apache.org/jira/browse/CURATOR-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman resolved CURATOR-426. -- Resolution: Fixed Fix Version/s: 4.0.0 > Prep Apache Curator 4.0.0 > ---

[GitHub] curator pull request #232: [CURATOR-426] Prep for Curator 4.0.0

Github user asfgit closed the pull request at: https://github.com/apache/curator/pull/232 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[jira] [Commented] (CURATOR-426) Prep Apache Curator 4.0.0

[ https://issues.apache.org/jira/browse/CURATOR-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097483#comment-16097483 ] ASF GitHub Bot commented on CURATOR-426: Github user asfgit closed the pull reque

Re: Jenkins and a release of Curator 4.0.0

Sounds ok to me On 23 Jul 2017 10:00 AM, "Jordan Zimmerman" wrote: > Hey, > > The existing Curator Jenkins project started failing in odd ways without a > clear reason. So, I renamed it "Curator Old" and made a new Jenkins project > that seems to work. The Current tests run (mostly - a tiny bit

[jira] [Commented] (CURATOR-313) Verify that Curator logging is appropriate

[ https://issues.apache.org/jira/browse/CURATOR-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097461#comment-16097461 ] Jordan Zimmerman commented on CURATOR-313: -- Yeah - in CuratorFrameworkImpl there

Jenkins and a release of Curator 4.0.0

Hey, The existing Curator Jenkins project started failing in odd ways without a clear reason. So, I renamed it "Curator Old" and made a new Jenkins project that seems to work. The Current tests run (mostly - a tiny bit of flakiness). However, occasionally, the new curator-test-zk34 fails at the

[jira] [Commented] (CURATOR-313) Verify that Curator logging is appropriate

[ https://issues.apache.org/jira/browse/CURATOR-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097455#comment-16097455 ] Jordan Zimmerman commented on CURATOR-313: -- Didn't you (I forget who) do some wo

[jira] [Assigned] (CURATOR-313) Verify that Curator logging is appropriate

[ https://issues.apache.org/jira/browse/CURATOR-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reassigned CURATOR-313: - Assignee: (was: Mike Drob) > Verify that Curator logging is appropriate > --

Jenkins build is back to normal : Curator #8

See

Jenkins build is back to normal : Curator » Curator ZooKeeper 3.4 Testing #8

See

Jenkins build is back to normal : Curator » Curator Testing #8

See

Jenkins build is back to stable : Curator » Curator Recipes #8

See

Build failed in Jenkins: Curator #6

See -- Started by user randgalt [EnvInject] - Loading node environment variables. Building remotely on ubuntu-6 (ubuntu trusty) in workspace Wiping out wo

Build failed in Jenkins: Curator » Curator Testing #6

See -- [INFO] [INFO]

Build failed in Jenkins: Curator » Curator ZooKeeper 3.4 Testing #5

See -- [INFO] [INFO] ---

Build failed in Jenkins: Curator #5

See -- Started by user randgalt [EnvInject] - Loading node environment variables. Building remotely on ubuntu-6 (ubuntu trusty) in workspace Wiping out wo

Jenkins build is still unstable: Curator 2 » Curator Recipes #4

See

Build failed in Jenkins: Curator 2 #4

See Changes: [randgalt] testSessionSurvives is a bit flakey. Add a connection state listener to [randgalt] Maven's incremental compiler was messing up some of the classes that are [randgalt] when retrying, output the

Build failed in Jenkins: Curator 2 » Curator ZooKeeper 3.4 Testing #4

See Changes: [randgalt] Maven's incremental compiler was messing up some of the classes that are -- [INFO]

Jenkins build is back to stable : Curator 2 » Curator Framework #4

See

Jenkins build is back to stable : Curator 2 » Curator Async #4

See

Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

I've proven that it works by running all the framework/recipe tests with the latest master but forcing ZooKeeper 3.4.8 as the client library and server (via curator-test 2.12.0). > On Jul 22, 2017, at 2:55 AM, Cameron McKenzie wrote: > > Sounds ok to me as long as the backwards compatibility i

Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

Thanks Cameron. I'll do the release, no worries. -JZ > On Jul 22, 2017, at 2:55 AM, Cameron McKenzie wrote: > > Sounds ok to me as long as the backwards compatibility is all good. I'm still > away for another couple of days, but I can do the release sometime next week > if you like. > cheers

Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

Sounds ok to me as long as the backwards compatibility is all good. I'm still away for another couple of days, but I can do the release sometime next week if you like. cheers On Thu, Jul 20, 2017 at 5:48 AM, Jordan Zimmerman < jor...@jordanzimmerman.com> wrote: > Folks, > > I was trying to backpo