+1
On Tue, Jun 25, 2013 at 3:41 AM, Sylvain Lebresne wrote:
> After having reverted CASSANDRA-5665, I propose the following artifacts for
> release as 1.2.6.
>
> sha1: a6ca5d496facf79c187310e81b3eeba3e6bc4b43
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags
+1
On Tue, Jun 25, 2013 at 9:14 AM, Jonathan Ellis wrote:
> Thanks for the confirmation, Michael.
>
> On Tue, Jun 25, 2013 at 6:28 AM, Michael Kjellman
> wrote:
> > I know non members aren¹t supposed to comment on these votes, but I was
> > actually throwing 1.2.6 Strike 2ish into production w
Thanks for the confirmation, Michael.
On Tue, Jun 25, 2013 at 6:28 AM, Michael Kjellman
wrote:
> I know non members aren¹t supposed to comment on these votes, but I was
> actually throwing 1.2.6 Strike 2ish into production when 3/4 of the way
> thru I got Jason¹s email as I was debugging Gossip i
+1
On Tue, Jun 25, 2013 at 3:41 AM, Sylvain Lebresne wrote:
> After having reverted CASSANDRA-5665, I propose the following artifacts for
> release as 1.2.6.
>
> sha1: a6ca5d496facf79c187310e81b3eeba3e6bc4b43
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tag
+1
Thanks,
Murali
On Jun 25, 2013 6:14 PM, "Jason Brown" wrote:
> +1 to the newest 1.2.6 build
>
> +1 to dtests saving the day
>
> +1 to anybody commenting on these votes. Micheal, I'm glad you were able to
> test (in prod? :) ) and verify there was indeed a problem, and for letting
> the commun
+1 to the newest 1.2.6 build
+1 to dtests saving the day
+1 to anybody commenting on these votes. Micheal, I'm glad you were able to
test (in prod? :) ) and verify there was indeed a problem, and for letting
the community know - and then testing the 'reverted' version.
On Tue, Jun 25, 2013 at
very nice, dtests win
+1
On Tue, Jun 25, 2013 at 1:28 PM, Michael Kjellman
wrote:
> I know non members aren¹t supposed to comment on these votes, but I was
> actually throwing 1.2.6 Strike 2ish into production when 3/4 of the way
> thru I got Jason¹s email as I was debugging Gossip issues acros
I know non members aren¹t supposed to comment on these votes, but I was
actually throwing 1.2.6 Strike 2ish into production when 3/4 of the way
thru I got Jason¹s email as I was debugging Gossip issues across the
cluster. It didn¹t appear to just break repair, but it also broke Gossip
(makes since
+1
On Jun 25, 2013 10:42 AM, "Sylvain Lebresne" wrote:
> After having reverted CASSANDRA-5665, I propose the following artifacts for
> release as 1.2.6.
>
> sha1: a6ca5d496facf79c187310e81b3eeba3e6bc4b43
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.
After having reverted CASSANDRA-5665, I propose the following artifacts for
release as 1.2.6.
sha1: a6ca5d496facf79c187310e81b3eeba3e6bc4b43
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.6-tentative
Artifacts:
https://repository.apache.org/content/repositor
Alright, fair enough. This vote is now close. I'll revert CASSANDRA-5665
and restart a new vote with that.
--
Sylvain
On Tue, Jun 25, 2013 at 9:12 AM, Jason Brown wrote:
> Hi all,
>
> I finally dug into the dtest error on repair_test.TestRepair (in
>
> http://buildbot.datastax.com:8010/builder
Hi all,
I finally dug into the dtest error on repair_test.TestRepair (in
http://buildbot.datastax.com:8010/builders/cassandra-1.2/builds/513/steps/shell/logs/stdio,
for example). Looking at the last successful run, and all the changes
since, I'm quite convinced the failure is due to a change I mad
12 matches
Mail list logo
