-1
Corey, I'm really sorry for the churn. I thought I ran both forward and
backward compatibility modes last time (-old 1.6.1 -new 1.6.2 as well as
-old 1.6.2 -new 1.6.1), but I must have just eyeballed the output of the
1.6.1 -> 1.6.2 report for problems with forward compatibility.
I ran things
Also, -1 due to the problems Sean identified.
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Sun, Jan 25, 2015 at 3:19 AM, Sean Busbey wrote:
> -1
>
> Corey, I'm really sorry for the churn. I thought I ran both forward and
> backward compatibility modes last time (-old 1.6.1 -new 1.
Another issue: the stated SHA1 does not match. The commit actually appears
to be: 03a3d18b9150fe7f42f024bbc0589c61609b5522
It looks like what happened was simply that you pushed the commit to bump
to 1.6.3-SNAPSHOT onto the rc2 branch accidentally.
--
Christopher L Tubbs II
http://gravatar.com/ct
-1 for backwards compatibility issues described.
-1
Corey, I'm really sorry for the churn. I thought I ran both forward and
backward compatibility modes last time (-old 1.6.1 -new 1.6.2 as well as
-old 1.6.2 -new 1.6.1), but I must have just eyeballed the output of the
1.6.1 -> 1.6.2 report for pr
plus, I don't think it's valid to call this vote on the user list :)
Corey Nolet wrote:
-1 for backwards compatibility issues described.
-1
Corey, I'm really sorry for the churn. I thought I ran both forward and
backward compatibility modes last time (-old 1.6.1 -new 1.6.2 as well as
-old 1.6.
