down. again.
> On Jun 14, 2016, at 11:14 AM, Alex Popescu wrote:
>
> I've been trying to get to a ticket for the last 2h and I only get service
> unavailable :-(
>
> On Tue, Jun 14, 2016 at 10:26 AM, Michael Kjellman <
> mkjell...@internalcircle.com> w
on-the-fly. We are
thinking to do a nodetool resetlocalschema to force the schema synchronization.
How safe is this method? Do we need to disable thrift/gossip protocol before
performing this function, and enable them back after resync completes?
Thanks in advance!
Sincerely,
Michael Fong
Hm... weird, JIRA isn't working again? S bizarre!! 😂
> On Jun 15, 2016, at 5:38 PM, Michael Kjellman
> wrote:
>
> down. again.
>
>> On Jun 14, 2016, at 11:14 AM, Alex Popescu wrote:
>>
>> I've been trying to get to a ticket for the la
iliarity
> with its mechanics and administration and, at worst, could put someone from
> ASF in touch with a colleague to get things running more smoothly.
>
> How can I/we help? :)
http://www.apache.org/dev/infra-contact
--
Kind regards,
Michael
On 06/26/2016 11:03 AM, Jonathan Ellis wrote:
>
> Is Snap a new packaging format like deb/rpm, or does it consume the
> existing deb package?
It's an LXD container delivery system.
--
Kind regards,
Michael
o for customized deployments.
> Aside: there's at 3 other reasonably popular projects called Snap; makes it
> hard to Google.
Yep, not a unique name choice, and this is blocking snapd transition to
Debian testing: https://bugs.debian.org/826884
--
Kind regards,
Michael
le slow, but it's there.
¯\_(ツ)_/¯
https://github.com/apache/cassandra/tree/cassandra-3.0.8
--
Kind regards,
Michael
I propose the following artifacts for release as 3.8.
sha1: c3ded0551f538f7845602b27d53240cd8129265c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1123/org/apache/cas
Thanks for the clarity, Jonathan. I agree that an August 3.8 release
target sounds like the most reasonable option, at this point in time.
With Sylvain's binding -1, this vote has failed.
--
Kind regards,
Michael Shuler
On 07/21/2016 05:33 PM, Jonathan Ellis wrote:
> I feel like the
I apologize for messing this vote up.
So, what should happen now? Drop RESULT from the subject and continue
discussion of alternatives and voting?
--
Kind regards,
Michael
On 07/27/2016 06:33 AM, Aleksey Yeschenko wrote:
> The difference is that those -1s were based on new informat
pmc
--
Kind regards,
Michael
On 07/28/2016 01:47 PM, Aleksey Yeschenko wrote:
> Jake was just swapping his vote +1 to -1.
>
> Swapping mine to -1 too, so that we have a binding -1 majority now.
>
> Let’s get #12236 in and then decide what to do.
>
> --
> AY
>
&g
On 08/03/2016 03:31 PM, Kant Kodali wrote:
> when are we moving from SEDA to TPC? any timeline or something that I can
> look out for?
>
You could follow the JIRA ticket parent and children, review patches,
etc. :) https://issues.apache.org/jira/browse/CASSANDRA-10989
--
Kind regards,
Michael
I'm a big fan of mailing lists, but google makes issues very findable for new
people to the project as JIRA gets indexed. They won't be able to find the same
thing on an email they didn't get -- because they weren't in the project in the
first place.
Mailing lists are good for broad discussion
aren’t the source of truth. They are. That’s not optional. If you are an ASF
project,
mailing lists are the source of truth. Period.
On 8/15/16, 11:01 AM, "Michael Kjellman"
mailto:mkjell...@internalcircle.com>> wrote:
I'm a big fan of mailing lists, but google m
The result is a thread
archive that contains a large amount of "wall of text" appearance,
making it difficult to pick out and follow the actual conversation
taking place. Please, fix your mail client.
--
Kind regards,
Michael
+1
Sent from my iPhone
On Aug 15, 2016, at 6:48 PM, Brandon Williams
mailto:dri...@gmail.com>> wrote:
So will I, if that happens, which has never happened in the last ~7 years.
On Mon, Aug 15, 2016 at 4:27 PM, Jeff Jirsa
mailto:jeff.ji...@crowdstrike.com>>
wrote:
On 8/15/16, 2:15 PM, "Marvi
usual.
Any objections to doing this push to 3.8 today, then again when we have
a green light on 3.9 release?
Thanks! Michael
On 08/16/2016 10:52 AM, Aleksey Yeschenko wrote:
> No objections, the plan sounds good to me.
>
> In addition to that, prep for pushing 3.0.9 out with 3.9.
Thanks. Yes, 3.0.9 is also up for release, without any branch song and
dance :)
--
Michael
It looks like Dave replied to your first email that he added your wiki
user to be able to edit pages. Did your login not work properly, or did
you get some sort of error editing the wiki?
(cc'ed directly, too)
--
Kind regards,
Michael
On 08/18/2016 08:15 AM, Danielle Blake wrote:
> Hi
Just wanted to say thank you publicly to Jonathan Ellis for his tireless work
making this community and software what it is. He's always been level headed
and I certainly wouldn't be where I am without his leadership.
So, Jonathan, thanks for all the fish.
best,
kjellman
Sent from my iPhone
Looks like some very nice progress here! Mucho Exciting!! 💃🏻💃🏻💃🏻
On Aug 22, 2016, at 10:44 PM, Joel Knighton
mailto:joel.knigh...@datastax.com>> wrote:
===
testall: All passed!
===
dtest: 2 failures
Awesome Joel
Sent from my iPhone
On Aug 24, 2016, at 8:22 PM, Joel Knighton
mailto:joel.knigh...@datastax.com>> wrote:
===
testall: All passed!
===
dtest: 2 failures
scrub_test.TestScrubIndexes
he job - I think this was the right
test :)
Thanks for looking!
Michael
mshuler@hana:~/tmp/logs$ ls -lRt
.:
total 2776
drwxr-xr-x 2 mshuler mshuler 12288 Aug 31 00:48 logs
-rw-r--r-- 1 mshuler mshuler 2825465 Aug 31 08:24
jenkins-trunk_testall-1153_logs.tar.gz
./logs:
total 31928
-rw-r--r-- 1 m
assandra-2.2_testall/578/console
This appears to have hung on the cql3.DropKeyspaceCommitLogRecycleTest
long-test, and failed to fetch logs.
--
Kind regards,
Michael
:41:17 2016 -0400
Fix Java Version check for versions > 100 on Windows (3.0 patch)
Patch by pmotta; reviewed by jmckenzie for CASSANDRA-12278
--
Kind regards,
Michael
27;d be happy to get extra details
and facilitate the setup with INFRA. Thanks!
--
Kind regards,
Michael
Dave asked, the INFRA ticket is
https://issues.apache.org/jira/browse/INFRA-12366
Thanks all!
Michael
What's preventing the use of the 3.6 or 3.7 releases where this bug is
already fixed? This is also fixed in the 3.0.6/7/8 releases.
Michael
On 09/14/2016 08:30 PM, Jonathan Haddad wrote:
> Unfortunately CASSANDRA-11618 was fixed in 3.6 but was not back ported to
> 3.5 as well, a
non-binding +1
Here's the testing summary on the 3.0.9-tentative tag:
http://12.am/tmp/3.0.9-tests.png
--
Michael
On 09/15/2016 01:57 PM, Jake Luciani wrote:
> I propose the following artifacts for release as 3.0.9.
>
> sha1: d600f51ee1a3eb7b30ce3c409129567b70c22012
> Git:
I hate that comment with a passion. Please please please please do yourself a
favor and *always* run with asserts on. `-ea` for life. In practice I'd be
surprised if you actually got a reliable 5% performance win and I doubt your
customers will care about a potential 5% performance win when you'
ot;
This is somewhat of my point. Why do assertions that sometimes are trapped
"protect my data" better then a checked exception?
On Wed, Sep 21, 2016 at 1:24 PM, Michael Kjellman <
mkjell...@internalcircle.com<mailto:mkjell...@internalcircle.com>> wrote:
I hate that commen
> IllegalStateException. Other times an class named "estimator" asserts when
> the "estimate" "overflows". This seem far away from the defined purpose of
> assert.
>
> The glaring issue is that it bubbles through try catch so it hardly makes
> me fee
ith the version edit? This sounds the most reasonable and workable
with the release build process. This actually does sound like it should
be 2 votes, since the commit sha will be different.. Thanks!
--
Kind regards,
Michael
The cassandra-2.2 branch looks stable, has a lot of bug fixes, and Tyler
had someone ask about a 2.2.8 release. Any objections to rolling this up
for a vote? http://cassci.datastax.com/view/cassandra-2.2/
--
Kind regards,
Michael
I propose the following artifacts for release as 2.2.8.
sha1: e9fe96f404b6a936ac5dbceb8f3934fe0d098a97
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.8-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1125/org/apache
There were no immediate objections and I didn't spot any in-progress
tickets for 2.2.8, so go vote!
--
Michael
Thanks! I'll do these release builds and start votes, first thing Monday
morning, unless I find some time on Sunday.
--
Michael
On 09/23/2016 05:15 PM, Aleksey Yeschenko wrote:
> Branch 3.8 off 3.9 with a commit that only changes the version in all
> appropriate places.
>
> T
Jonathan's is a pretty compelling perspective.
--
Michael
On 09/23/2016 07:04 PM, Aleksey Yeschenko wrote:
> Both are effectively 3.9 on steroids. One month of features and
> improvements with 2 months of bug fixes on top.
>
> If anything, this overdelivers.
>
> --
,
and I need to be up early for an event tomorrow. I'll build both
releases Monday or sooner and get votes going.
--
Michael
On 09/24/2016 12:05 AM, Aleksey Yeschenko wrote:
> Please don’t make me argue over 3.8/3.9 again. We are way, way over
> our original schedule at this point.
>
[2]: (NEWS.txt) https://goo.gl/Aen2iN
--
Kind regards,
Michael
[2]: (NEWS.txt) https://goo.gl/1w6Ec1
--
Kind regards,
Michael Shuler
Jon, is there a JIRA ticket for this request? I appreciate everyone's
input, and I think this is a fine proposal.
--
Kind regards,
Michael
On 09/14/2016 08:30 PM, Jonathan Haddad wrote:
> Unfortunately CASSANDRA-11618 was fixed in 3.6 but was not back ported to
> 3.5 as well, a
I foresee many arithmetic errors with 3.X.. :)
--
Michael
On 09/27/2016 05:18 AM, Sylvain Lebresne wrote:
> We have a number of tickets that we now have to wait on 4.0 due to needing a
> messaging protocol change or major sstable format (https://goo.gl/OvqNQp),
> and
> we curre
With 7 binding, 1 non-binding +1 votes and no -1's, the 2.2.8 release
vote passes. I will get the artifacts released. Thanks!
--
Michael
On 09/26/2016 08:12 AM, Gary Dusbabek wrote:
> +1
>
> On Fri, Sep 23, 2016 at 6:04 PM, Michael Shuler wrote:
>
>> I propose the
* NOTICE *
This is the first release signed with key 0xA278B781FE4B2BDA by Michael
Shuler. Debian users will need to add the key to `apt-key` and the
process has been updated on
https://wiki.apache.org/cassandra/DebianPackaging and patch created for
source docs.
Either method will work
Thanks! To clarify, yes, I was just being silly. We mostly use the
base.version in build.xml for version checking and we can special-case
branch names like we do for trunk, if the needed.
--
Michael
On 09/29/2016 08:17 AM, Sylvain Lebresne wrote:
> And of course I've been retarded and c
The votes were 8 +1 binding, 1 +1 non-binding, and no -1 votes. I will
get the release published.
--
Kind regards,
Michael
On 09/26/2016 09:52 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.8.
>
> sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607
>
The votes were 8 +1 binding, 1 +1 non-binding, and no -1 votes. I will
get the release published.
--
Kind regards,
Michael
On 09/26/2016 10:12 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.9.
>
> sha1: c1fa21458777b51a9b21795330ed6f298103b436
>
The votes were 8 +1 binding, 1 +1 non-binding, and no -1 votes. I will
get the release published.
--
Kind regards,
Michael
(with RESULT subject, this time)
On 09/26/2016 10:12 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.9.
>
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.8.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source and
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.9.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source and
+1
On 09/30/2016 02:07 PM, Jason Brown wrote:
> +1
>
> On Fri, Sep 30, 2016 at 11:53 AM, Brandon Williams wrote:
>
>> +1
>>
>> On Fri, Sep 30, 2016 at 1:51 PM, Nate McCall wrote:
>>
>>> I propose we begin the process of accepting the contribution of the
>>> dtest codebase (https://github.com/r
I propose the following artifacts for release as 2.1.16.
sha1: 87034cd05964e64c6c925597279865a40a8c152f
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.16-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1129/org/apac
terday and adjusted fixver to 2.2.x+,
but had not seen this list message until this morning.
--
Kind regards,
Michael
Including myself, I count 8 +1 votes and no -1 votes for this release.
I'll get the release published!
--
Kind regards,
Michael
On 10/05/2016 06:09 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 2.1.16.
>
> sha1: 87034cd05964e64c6c925597279865a4
Nate, do think CASSANDRA-12758 should go to 2.1.x?
--
Michael
On 10/10/2016 02:26 PM, Nate McCall wrote:
> Hi Romain,
> I appreciate you speaking up about this, but I stuck with my +1 in
> order to get 2.1.16 with the NTR fix out since I have seen
> CASSANDRA-11363 with every r
and go into the next 2.1 release, or leave it for 2.2+?
--
Kind regards,
Michael
On 10/10/2016 03:09 PM, Nate McCall wrote:
>> It's too minor for a re-roll, and safe enough to just apply yourself if you
>> want it.
>
> Agreed.
>
>>
>> On Mon, Oct 10, 2016 a
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.1.16.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
There was a bunch of tests hastily and messly commented out line by line
(*whyy?*) ColumnFamilyStoreTest with comments that they are pending
SuperColumns support post 8099.
Could those responsible please cleanup after themselves? It's been a while
since 8099 was committed in the first place an
We use posix_fadvise in a bunch of places, and in stereotypical Cassandra
fashion no comments were provided.
There is a check the OS is Linux (okay, a start) but it turns out the behavior
of providing a length of 0 to posix_fadvise changed in some 2.6 kernels. We
don't check the kernel version
cid:543B66BF-5E99-4227-A24D-1AB8C0341D97@localhost]
best,
kjellman
On Oct 18, 2016, at 8:33 AM, Benedict Elliott Smith
mailto:bened...@apache.org>> wrote:
... and continuing in the fashion of behaviours one might like to disabuse
people of, no code link is provided.
On 18 October 201
ewhere.
>
> On Oct 18, 2016 11:29 AM, "Michael Kjellman"
> wrote:
>
>> We use posix_fadvise in a bunch of places, and in stereotypical Cassandra
>> fashion no comments were provided.
>>
>> There is a check the OS is Linux (okay, a start) but it turns
Specifically regarding the behavior in different kernels, from `man
posix_fadvise`: "In kernels before 2.6.6, if len was specified as 0, then this
was interpreted literally as "zero bytes", rather than as meaning "all bytes
through to the end of the file"."
On Oct
commented tests. My branch is going
> to be ready for review soon.
>
> [1] https://issues.apache.org/jira/browse/CASSANDRA-12373
>
>
> On Tue, Oct 18, 2016 at 5:10 PM Michael Kjellman <
> mkjell...@internalcircle.com> wrote:
>
>> There was a bunch of tests has
Within a single SegmentedFile?
On Oct 18, 2016, at 9:02 AM, Ariel Weisberg
mailto:ariel.weisb...@datastax.com>> wrote:
With compaction there can be hot and cold data mixed together.
I'm working on writing Birch for trunk and I noticed the following:
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/columniterator/AbstractSSTableIterator.java#L503
Prior to 3.0 the offset was the literal offset into the data file, yet now we
seem to be doing the
Cool, as I would have assumed they would need to be. Given they were initially
commented out on 6/30/15 maybe cleanup and removal of that dead code is still
at least warranted.
On Oct 18, 2016, at 9:15 AM, Oleksandr Petrov
mailto:oleksandr.pet...@gmail.com>> wrote:
Unit tests will be completel
On Tue, Oct 18, 2016 at 11:59 AM, Michael Kjellman <
mkjell...@internalcircle.com<mailto:mkjell...@internalcircle.com>> wrote:
Specifically regarding the behavior in different kernels, from `man
posix_fadvise`: "In kernels before 2.6.6, if len was specified as 0, then
this was in
Sorry, No. Always document your assumptions. I shouldn't need to git blame a
thousand commits and read thru a billion tickets to maybe understand why
something was done. Clearly thru the conversations on this topic I've had on
IRC and the responses so far on this email thread it's not/still not
Ugh, just finally figured the "header" bit of my question out. Mega lame. :\
> On Oct 18, 2016, at 9:17 AM, Michael Kjellman
> wrote:
>
> I'm working on writing Birch for trunk and I noticed the following:
>
> https://github.com/apache/cassandra/blob/trunk
I propose the following artifacts for release as 3.10.
sha1: a3828ca8b755fc98799867baf07039f7ff53be05
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1130/org/apache/c
I propose the following artifacts for release as 3.0.10.
sha1: 817ba038783212b716f6981b26c8348ffdc92f59
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1131/org/apac
I am changing my vote to -1 and closing this vote for the regression
reported in CASSANDRA-12867 by Kurt Greaves, which also affects 3.0.10.
For the record, I count 3 binding +1 votes and 3 binding -1 votes.
--
Kind regards,
Michael
On 10/31/2016 11:12 AM, Michael Shuler wrote:
> I propose
0, so help
getting that reviewed and committed would be great! I'll rebuild another
release set when that is completed.
--
Kind regards,
Michael
On 10/31/2016 10:18 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.10.
>
> sha1: a3828ca8b755fc9879986
@Chris: instead of promoting the arguing going on on this thread could you
please help lead by example and reply to Kelly's questions in her email?
Thanks.
I don't enjoy watching a community I care about continue to explode in front of
my eyes ☹️
best,
kjellman
Sent from my iPhone
> On Nov
Hi Kelly-
I can't speak to many of your questions as it's not my position to do so. What
I can say is that at Apple we are doubling down on open source. We have tons of
code in flight -- really big ones in fact -- many already out for review. Our
list of enhancements we want to do grows all the
gt; for the Apache Cassandra PMC and community to reply as well.
>
> Cheers,
> Chris
>
>
>> On 2016-11-04 10:14 (-0700), Michael Kjellman
>> wrote:
>> @Chris: instead of promoting the arguing going on on this thread could you
>> please help lead by examp
"Avalon. The database" yes autocorrect. That's exactly what I wanted.
That should read "scaling the database and stability." Sorry. I'm typing this
while walking up a big ass hill in San Francisco heading to the office. 😜
Sent from my iPhone
> On Nov 4, 20
eatures already
in releases for people to adopt so we've got the "features" thing under control
for at least a year in my opinion.
best,
kjellman
Sent from my iPhone
> On Nov 4, 2016, at 10:33 AM, Michael Kjellman
> wrote:
>
> "Avalon. The database
gs.
Thanks for the interest!
--
Kind regards,
Michael
Thanks Jeff for your thoughtful comments. +100
Sent from my iPhone
> On Nov 5, 2016, at 6:26 PM, Jeff Jirsa wrote:
>
> I hope the other 7 members of the board take note of this response,
> and other similar reactions on dev@ today.
>
> When Datastax violated trademark, they acknowledged it and
+1
On 11/06/2016 11:11 PM, Jeff Jirsa wrote:
> There exists a nearly unused mailing list, client-...@cassandra.apache.org
> [0].
>
> This is a summary of the email threads over the past 12 months on that list:
>
> 1) ApacheCon Seville CFP Close notice
> 2) Datastax .NET driver question
> 3) D
If someone could set the user MichaelShuler as admin, I can help with
user requests, such as the the current request on the list to add winguzone.
--
Michael
On 11/06/2016 11:59 PM, Vladimir Yudovin wrote:
> Please add user winguzone to Wiki,
Done. Thanks!
--
Michael
Yes, We hit this as well. We have a internal patch that I wrote to mostly
revert the behavior back to ByteBuffers with as small amount of code change as
possible. Performance of our build is now even with 2.0.x and we've also
forward ported it to 3.x (although the 3.x patch was even more complic
I propose the following artifacts for release as 3.0.10.
sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1132/org/apac
I propose the following artifacts for release as 3.10.
sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1133/org/apache/c
I think cassandra-3.0 HEAD is good with me, too. We can adjust the
fixver for those that may say 3.0.11 currently.
--
Michael
On 11/11/2016 08:31 AM, Jake Luciani wrote:
> Should I merge the fix to just the 3.0.10 tag? or should we include the 3
> new tickets that went into 3.0.11 alre
Thanks for all the feedback, I'm changing to a -1, too.
Vote comes to 1 binding +1, 3 binding -1, 3 non-binding -1.
--
Kind regards,
Michael
On 11/08/2016 02:09 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.10.
&
For the record, I'm changing my vote to a -1, as well.
--
Michael
On 11/11/2016 09:40 AM, Michael Shuler wrote:
> I think cassandra-3.0 HEAD is good with me, too. We can adjust the
> fixver for those that may say 3.0.11 currently.
>
backporting, and it will be tiny. It may also allow a
lower barrier for contributors interested in helping with specifically
build/test infrastructure.
Thanks!
Michael
On 11/11/2016 01:02 PM, Nate McCall wrote:
>> It may also allow a
>> lower barrier for contributors interested in helping with specifically
>> build/test infrastructure.
>
> Good point for new repo.
Requested a new 'cassandra-builds' git repo! Thanks.
--
Michael
I count 3 binding +1, 1 non-binding +1, and 3 binding -1 votes. I'll
re-roll a new release, since the CASSANDRA-11039 fix has already been
committed.
--
Kind regards,
Michael
On 11/08/2016 02:08 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.10.
&
I propose the following artifacts for release as 3.0.10.
sha1: d6a3ef4863142c3f9fc1def911f28341fc78f2e8
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1134/org/apac
With 6 binding, 1 non-binding +1 votes and no -1 votes, this release
vote passes. I will get the artifacts published.
--
Kind regards,
Michael
On 11/11/2016 07:36 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.10.
>
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.10.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
I propose the following artifacts for release as 3.10.
sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1135/org/apache/c
Honest question: are you *ever* positive Ed?
Maybe give it a shot once in a while. It will be good for your mental health.
Sent from my iPhone
> On Nov 19, 2016, at 11:50 AM, Edward Capriolo wrote:
>
> This is especially relevant if people wish to focus on removing things.
>
> For example,
Jason has asked for review and feedback many times. Maybe be constructive and
review his code instead of just complaining (once again)?
Sent from my iPhone
> On Nov 19, 2016, at 1:49 PM, Edward Capriolo wrote:
>
> I would say start with a mindset like 'people will run this in production'
> not
m the
cassandra-3.11 branch.
--
Kind regards,
Michael
On 11/18/2016 12:08 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.10.
>
> sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs
201 - 300 of 643 matches
Mail list logo
