Ok, I guess I'll put something in the versions section on curator.apache.org
cheers
On Tue, Jun 21, 2016 at 6:08 AM, Mike Drob wrote:
> Yea, as long as you doc it somewhere, it shouldn't be a blocker.
>
> On Sat, Jun 18, 2016 at 4:59 PM, Cameron McKenzie
> wrote:
>
> > That's fine with me. You
Yea, as long as you doc it somewhere, it shouldn't be a blocker.
On Sat, Jun 18, 2016 at 4:59 PM, Cameron McKenzie
wrote:
> That's fine with me. You OK with it Mike?
> On 19 Jun 2016 1:21 AM, "Jordan Zimmerman"
> wrote:
>
> > Can we solve this at a different time? People are waiting on this rel
Thanks Jay,
Trying to make the 3.2.0 tests more reliable is on my list of things to do.
I also had some intermittent failures when running them.
cheers
On Mon, Jun 20, 2016 at 4:15 PM, Jay Zarfoss wrote:
> +1
>
> Will note that there is still some test flakiness in 3.2.0; I had to run
> these tw
+1
Will note that there is still some test flakiness in 3.2.0; I had to run
these two a few times before I got green:
testLostSession(org.apache.curator.framework.imps.TestFailedDeleteManager)
Time elapsed: 27.425 sec <<< FAILURE!
testWithNamespaceAndLostSessionAlt(org.apache.curator.framework.
+1 Binding
Please - other committers - vote on this release. It's very important.
Take a few moments to vote.
-Jordan
On Sun, Jun 19, 2016 at 8:08 PM, Cameron McKenzie
wrote:
> Hello,
>
> This is a combined vote to release Apache Curator versions 2.11.0 and 3.2.0
>
> *** Please download, test a
Hello,
This is a combined vote to release Apache Curator versions 2.11.0 and 3.2.0
*** Please download, test and vote within approx. 72 hours
Note that we are voting upon the source (tag) and binaries are
provided for convenience.
Link to release notes:
2.1.11 -
*https://issues.apache.org/jira
That's fine with me. You OK with it Mike?
On 19 Jun 2016 1:21 AM, "Jordan Zimmerman"
wrote:
> Can we solve this at a different time? People are waiting on this release
> and the version number will not affect their applications one bit.
>
> -Jordan
>
> > On Jun 18, 2016, at 4:31 AM, Cameron McKen
Can we solve this at a different time? People are waiting on this release and
the version number will not affect their applications one bit.
-Jordan
> On Jun 18, 2016, at 4:31 AM, Cameron McKenzie wrote:
>
> I can see both points of view. In an ideal world we would use the proper
> definition
I can see both points of view. In an ideal world we would use the proper
definition of semantic versioning, but pragmatically, I think that it is
going to be difficult to maintain with 2 concurrent sets of releases. So, I
think that we should just tried with the version numbers suggested.
Thoughts?
I’m very much against bumping the major version number. We’re using the major
version number to indicate compatibility with ZooKeeper. Historically, the
middle number has represented API compatibility for Curator. There’s no reason
to change now. We can revisit in the future.
-Jordan
> On Jun
Thanks Mike, I will rebuild and get rid of the bin and test directories. In
regards to the incompatibilities generated by clirr, what's the go? Should
we not be making any incompatible API changes without incrementing the
major version number? In that case I guess we need to revert that changed
the
-1
Downloaded artifacts from staging repos.
Signatures are good.
Checksums are good.
Source zips does not match tag:
$ diff --recursive . /tmp/curator/2.11/apache-curator-2.11.0/
Only in /tmp/curator/2.11/apache-curator-2.11.0/curator-framework:
test-output
Only in /tmp/curator/2.11/apache-curat
Signatures on both files match
+1 Binding
On Wed, Jun 15, 2016 at 3:18 AM, Cameron McKenzie
wrote:
> Hello,
>
> This is a combined vote to release Apache Curator versions 2.11.0 and 3.2.0
>
> *** Please download, test and vote within approx. 72 hours
>
> Note that we are voting upon the source (
Hello,
This is a combined vote to release Apache Curator versions 2.11.0 and 3.2.0
*** Please download, test and vote within approx. 72 hours
Note that we are voting upon the source (tag) and binaries are
provided for convenience.
Link to release notes:
2.1.11 -
*https://issues.apache.org/jira
14 matches
Mail list logo
