+1
On Fri, 18 Apr 2025 at 3:59 AM, Josh McKenzie wrote:
> [DISCUSS] thread:
> https://lists.apache.org/thread/jy6vodbkh64plhdfwqz3l3364gsmh2lq
>
> The proposed new versioning mechanism:
>
>1. We no longer use semver .MINOR
>2. Online upgrades are supported for all GA supported releases a
100% a hold over from thrift - I don't remember who i was discussing this
with ages ago, but there was definitely some question about whether it
would bite us eventually.
On Wed, Feb 12, 2025 at 8:28 AM Jeremiah Jordan
wrote:
> AFAIK this EMPTY stuff goes back to thrift days. We let people inse
+1
On Tue, Mar 18, 2025 at 9:14 PM Mick Semb Wever wrote:
> (general@incubator cc'd)
>
> Please vote on the acceptance of the Spark-Cassandra-Connector and its
> IP Clearance:
>
> https://incubator.apache.org/ip-clearance/cassandra-spark-cassandra-connector.html
>
> All consent from original aut
It sounds like we are all pretty interested in seeing this feature land and
the branch maintenance is causing overhead that could be spent on
finalisation. +1 on merging, particularly given the feature flag work.
Once more unto the breach 💪
On Fri, 7 Mar 2025 at 6:56 PM, Benedict wrote:
> There
+1
Verified sigs and artifact coordinates.
On Tue, Feb 11, 2025 at 12:30 PM Brandon Williams wrote:
> +1
>
> Checked sha/sig, maven artifacts, built on j8.
>
> Kind Regards,
> Brandon
>
> On Thu, Feb 6, 2025 at 4:34 PM Bret McGuire
> wrote:
> >
> >Greetings all! I’m proposing the test buil
I feel like a group of us discussed this IRL a bit at ApacheCon in Vegas ~
2019 maybe? Anyhoo, the tidbit sticking in my mind was someone explaining
the string operations overhead in the JVM of log concatenation vs slapping
binary to CQ’s off heap-and-append operation was substantial.
We could hos
Hi Jackson,
Thanks for bringing this up. You all run enough C* over there to have a
good idea of what's needed. If you want to move your instances to ARM, I
think that's totally fine and agree that we need the coverage anyway.
Cheers,
-Nate
On Fri, May 24, 2024 at 10:52 AM Fleming, Jackson via de
We've talked through this before. Benjamin sussed out the main issue, IIRC.
tl,dr:
- The AUTHORS lists everyone who ever made a commit (
https://github.com/gocql/gocql/blob/master/AUTHORS)
- The license is BSD-3 and explicitly says the copyright is owned by the
authors (https://github.com/gocql/goc
On Thu, Nov 30, 2023 at 3:28 AM Aleksey Yeshchenko
wrote:
> -1 on cutting a beta1 in this state. An alpha2 would be acceptable now,
> but I’m not sure there is significant value to be had from it. Merge the
> fixes for outstanding issues listed above, then cut beta1.
>
Agree with Aleksey. -1 on
> Even though my opinion doesn't really count here, I do feel compelled to
> mention that:
>
Aaron (and anybody who takes the time to follow this list, really), your
opinion matters, that's why we discuss it here.
+1
On Tue, Oct 3, 2023 at 5:53 PM Mick Semb Wever wrote:
> The donation of the java-driver is ready for its IP Clearance vote.
> https://incubator.apache.org/ip-clearance/cassandra-java-driver.html
>
> The SGA has been sent to the ASF. This does not require acknowledgement
> before the vote.
>
On Fri, Jul 21, 2023 at 10:56 AM Miklosovic, Stefan <
stefan.mikloso...@netapp.com> wrote:
...
> I think this might work, if it is available, it will use it, if not, we
> emit a big fat warning.
>
...
I agree with this approach. It lets operators trap a log statement or
similar while defaulting t
+1
On Wed, Jun 28, 2023 at 5:17 AM Shailaja Koppu wrote:
> Hi Team,
>
> (Starting a new thread for VOTE instead of reusing the DISCUSS thread, to
> follow usual procedure).
>
> Please vote on CEP 33 - CIDR filtering authorizer
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-33%3A+CID
Hi Shailaja,
This looks super interesting. I particularly like the MONITOR switch. This
is a huge pain-point for a lot of cluster migrations.
Cheers,
-Nate
On Thu, Jun 15, 2023 at 6:43 AM Shailaja Koppu wrote:
> Hi Team,
>
> I have created CEP 33 - CIDR filtering authorizer
> https://cwiki.apac
+1
On Wed, Jun 14, 2023 at 2:15 AM Jeremy Hanna
wrote:
> Calling for a vote on CEP-8 [1].
>
> To clarify the intent, as Benjamin said in the discussion thread [2], the
> goal of this vote is simply to ensure that the community is in favor of
> the donation. Nothing more.
> The plan is to introdu
+1
Thanks Doug!
On Fri, May 5, 2023 at 4:47 AM Doug Rohrer wrote:
> Hello all,
>
> I’d like to put CEP-28 to a vote.
>
> Proposal:
>
>
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-28%3A+Reading+and+Writing+Cassandra+Data+with+Spark+Bulk+Analytics
>
> Jira:
> https://issues.apach
Thank you for your effort regardless, Lorina. Very much appreciated!
On Tue, Apr 4, 2023 at 6:39 AM lorinapoland wrote:
> Sadly, I am informing the community that our grant application to GSoD was
> unsuccessful.
>
> If you would like to see the list of winning projects, check out
> https://deve
>
>
> Are there any objections to this approach?
>
>
Linking to a podcast is just like linking to a presentation or a blog entry
back in the day. As long as the trademark keeps being respected (good
effort so far!) I don't see any issue with it. Thanks for taking initiative
on this, Aaron.
-Nate
+1
On Tue, Nov 16, 2021 at 8:43 AM Branimir Lambov wrote:
> Hi everyone,
>
> I would like to start a vote on this CEP.
>
> Proposal:
>
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-17%3A+SSTable+format+API
>
> Discussion:
>
> https://lists.apache.org/thread.html/r636bebcab4e678dbe
On Sat, Oct 16, 2021 at 7:18 AM Jonathan Ellis wrote:
> ...
> *This work shall be developed in a modular manner, to allow for coexistence
> with other consensus protocols or transaction managers. This will allow us
> to evolve Accord without precluding alternative solutions, as future work
> expa
Hi Benedict,
If I'm parsing this correctly, you want to include the stand-alone library
in the project as a separate repo to begin with, correct? (I'm +1 on that,
if so).
Otherwise I am very intrigued by the paper and proposal. This looks
excellent. Thanks Benedict, et all for putting this togethe
+1
On Wed, Sep 1, 2021 at 11:55 PM Sam Tunnicliffe wrote:
> Proposing the test build of Cassandra 4.0.1 for release.
>
> sha1: 6709111ed007a54b3e42884853f89cabd38e4316
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative
> Maven Artifacts:
> https:
>
>
> Last but not least, do we know anyone running Java 11 in production?
> This thread was really opened as a stage to share our thoughts and
> hopefully come up with a plan as a community.
>
I am aware of many large deployments using Java11 and 4.0 in production. +1
on making this non experime
+1
On Mon, Jul 26, 2021 at 7:06 AM Brandon Williams wrote:
> I am proposing the test build of Cassandra 3.11.11 for release.
>
> sha1: 4cafe2288e56e1135d65e76adbcd6c2de9306d6b
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.11-tentative
> Maven Artifacts
+1
On Fri, Jul 23, 2021 at 10:41 AM Brandon Williams <
brandonwilli...@apache.org> wrote:
> I am proposing the test build of Cassandra 4.0.0 for release.
>
> sha1: 902b4d31772eaa84f05ffdc1e4f4b7a66d5b17e6
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.0-
Yay for pluggable memtables!! I havent gone over this in detail yet, but
personally I've always thought integrating something like Arrow would be
cool for sharing data (that's as far as i've gotten, but anything that
makes that kind of experimentation easier would also help with mocking test
plumbi
>
>
>
> > Yes, we should perhaps remove target version from the template, and
> > introduce guidance on describing stability impact etc.
>
> Strong +1 to remove this from the template. I got sucked into the mistake
> of conflating implementation details and implications on where it lands
> instead
+1
On Wed, Jul 14, 2021 at 2:49 AM Benjamin Lerer wrote:
> Hi everyone,
>
> I am proposing the CIP-9 (Make SSLContext creation pluggable) for adoption
>
> Discussion thread:
>
> https://lists.apache.org/thread.html/rbf99c0108a65f5e31a8f8f0ee525816ee0a387a6fae64de86ceb1495%40%3Cdev.cassandra.apa
On Fri, Jun 4, 2021 at 8:53 AM Ekaterina Dimitrova
wrote:
> One more point - if we keep the workaround, that should be documented with
> big red letters for the users.
>
>
Agree with addressing this with some docs.
Good catch, Stefan. Per your question on obsfucation - IMO, IME passwords
should
Hi Maulin,
Thanks for putting this together!
Took a quick glance, and I can't think of a compelling reason on why
SSLContext should be final and your point about organization/compliance
issues requiring different implementations is a good one.
Per #3 on your proposed changes, I'm keen to only sup
+1
On Thu, Apr 22, 2021 at 6:59 AM Mick Semb Wever wrote:
> Proposing the test build of Cassandra 4.0-rc1 for release.
>
> sha1: 3282f5ecf187ecbb56b8d73ab9a9110c010898b0
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-rc1-tentative
> Maven Artifacts:
>
>
Agree with Stefan 100% on this. We need to move towards pluggability. Our
users are asking for it, it makes sense architecturally, and people are
doing it anyway.
...
> for me definitely https://issues.apache.org/jira/browse/CASSANDRA-9633
>
> I am surprised nobody mentioned this in the previous
+1
On Tue, Mar 30, 2021 at 2:06 AM Mick Semb Wever wrote:
> Proposing the test build of Cassandra 4.0-rc1 for release.
>
> sha1: 2facbc97ea215faef1735d9a3d5697162f61bc8c
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-rc1-tentative
> Maven Artifacts:
>
Thanks Melissa! This looks really good. Excited to see it happen.
On Sat, Feb 27, 2021 at 10:36 AM Melissa Logan
wrote:
> Hi all,
>
> We are excited to share the almost-complete Cassandra website design
> (CASSANDRA-16115). Huge thanks to Lorina Poland, Anthony Grosso, Mick Semb
> Weaver, Josh L
Just make sure there is some good detail present in NEWS.txt on the impact
and needed changes if someone is anticipating those metrics being present.
On Fri, Oct 30, 2020 at 8:53 AM Sam Tunnicliffe wrote:
> In CASSANDRA-15299, native protocol V5 is being reworked to incorporate
> the framing for
+1
On Thu, Oct 8, 2020 at 9:20 PM Oleksandr Petrov
wrote:
> Proposing the test build of in-jvm dtest API 0.0.6 for release.
>
> Repository:
>
> https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.6
>
> Candidate SHA:
>
> https://github.com/apache/cassa
+1
On Wed, Sep 16, 2020 at 9:46 PM Mick Semb Wever wrote:
> This vote is about officially accepting the Harry donation from Alex Petrov
> and Benedict Elliott Smith, that was worked on in CASSANDRA-15348.
>
> The Incubator IP Clearance has been filled out at
> http://incubator.apache.org/ip-clea
Thanks for bringing this up again, Paulo!
Moving ApacheCon to online turned out to be complicated logistically, so we
just did a single C* track. Would be happy to help organize an NGCC though.
On Mon, Sep 14, 2020 at 12:40 PM Paulo Motta wrote:
> Hey folks,
>
> Nate mentioned on this thread [1
+1
On Sat, Aug 29, 2020 at 1:38 AM Mick Semb Wever wrote:
> Proposing the test build of Cassandra 3.11.8 for release.
>
> sha1: 8b29b698630960a0ebb2c695cc5b21dee4686d09
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.8-tentative
> Maven Artifacts:
>
> h
+1
On Sat, Aug 29, 2020 at 12:45 AM Mick Semb Wever wrote:
> Proposing the test build of Cassandra 2.2.18 for release.
>
> sha1: d4938cf4e488a9ef3ac48164a3e946f16255d721
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.18-tentative
> Maven Artifacts:
>
>
+1
On Sat, Aug 29, 2020 at 1:10 AM Mick Semb Wever wrote:
> Proposing the test build of Cassandra 3.0.22 for release.
>
> sha1: 45331bb612dc7847efece7e26cdd0b376bd11249
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.22-tentative
> Maven Artifacts:
>
> h
+1
On Sat, Aug 29, 2020 at 2:19 AM Mick Semb Wever wrote:
> Proposing the test build of Cassandra 4.0-beta2 for release.
>
> sha1: 56eadf2004399a80f0733041cacf03839832249a
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta2-tentative
> Maven Artifacts:
>
>
>
> 901 practitioners were interviewed. I analyzed the data and summarized in a
> document here:
>
> https://docs.google.com/document/d/1aM8muvbldPhSJdgrsM0OiLGvb5wfjwc5uutSCNfGup8/edit?usp=sharing
>
> If this seems broadly useful, I’m proposing that we publish to the C* blog.
> New graphics wi
This is a really interesting idea, particularly given that at this point in
our release cycle previously, there would be demos/roadshows happening at
meetups etc. that we just cant do these days in most places now.
What is your thinking on format?
+1 in general though - that goes for anybody that
This is fantastic, Alexandre, thanks for putting this together!
I put an initial set of comments/concerns on there and will loop back later
this week after other folks have a go.
Cheers,
-Nate
On Sat, Jul 25, 2020 at 7:35 AM Alexandre Dutra <
alexandre.du...@datastax.com> wrote:
> Hi,
>
> As p
>
> Count me in. Happy to assist.
>
> I mean, I basically did already since you were my right hand with this
last year :)
Per my previous email:
2. Decide what we want to do about NGCC
3. Add some more talks as we go depending on demand
4. Figure out the logistics of how this will work by playing with Hopin
Again, this is pretty much a blank slate. Assume we have a virtual
conference system for 24hrs and can basical
Hi folks,
ApacheCon@Home Cassandra track finally coming together. We have a little
over 20 submissions to go through initially this week to put together a
rough schedule.
This year, we will be using Hopin for managing the conference track. That's
about as much as I know about logistics at this poi
Agree as well. Happy to have anything like this on a community downloads
page provided the license isnt anything weird.
Evaluation with a website PR and a JIRA should suffice?
On Fri, Jul 10, 2020 at 4:51 AM Jon Haddad wrote:
> I agree with Josh about it going on the downloads page - I don't th
>
>
>
> If so, I propose we set this thread down for now in deference to us
> articulating the quality bar we set and how we achieve it for features in
> the DB and then retroactively apply them to existing experimental features.
> Should we determine nobody is stepping up to maintain an
> experime
On Wed, Jul 1, 2020 at 10:27 AM David Capwell wrote:
> If that is the case then shouldn't we add MV to "4.0 Quality: Components
> and Test Plans" (CASSANDRA-15536)? It is currently missing, so adding it
> to the testing road map would be a clear sign that someone is planning to
> champion and ow
+1
On Sun, Jun 21, 2020 at 3:12 AM Joshua McKenzie
wrote:
> Link to doc:
>
> https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Project+Governance
>
> Change since previous cancelled vote:
> "A simple majority of this electorate becomes the low-watermark for votes
> in favour
+1 (binding)
On Wed, Jun 17, 2020 at 4:19 AM Joshua McKenzie
wrote:
> Added unratified draft to the wiki here:
>
> https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Project+Governance
>
> I propose the following:
>
>1. We leave the vote open for 1 week (close at end of d
If you had an environment available, I would be real curious about what
happens when you start it up, particularly when we started writing larger
SSTables.
That said, I don't think we've fielded this question in like 8yrs, so I
doubt there is any interest in supporting it if it doesnt just kind of
I agree with Benedict. We have a lot of organizational things going on
right now, perhaps we just mark it as deprecated in the docs and reference
alternatives in the readme? Then we can put this on a roadmap to revisit
post 4.0.
On Fri, May 1, 2020 at 7:50 AM Benedict Elliott Smith
wrote:
> I v
>
>
> Lastly, and to Stephen's previous email, it might be more manageable to
> accept one drivers first and figure all the details/issues/questions that
> are bound to arise before accepting more. It's worth discussing at least.
>
This approach makes complete sense to me: let's sort out how to ac
o undermine
> that
> > >> >> capability, as people begin to assume that activity and
> > >> decision-making is
> > >> >> unrelated to them - and if that happens I think something important
> > is
> > >> lost.
> > >> >
On Thu, Apr 23, 2020 at 5:37 AM Benedict Elliott Smith
wrote:
> I welcome the donation, and hope we are able to accept all of the
> drivers. This is really great news IMO.
>
> I do however wonder if the project may be accumulating too many
> sub-projects? I wonder if it's time to think about s
nity.
> > >
> > > During the process of developing software and preparing a release,
> > various packages are made available to the development community for
> > testing purposes. Projects MUST direct outsiders towards official
> releases
> > rather than raw sou
Open an issue with the LEGAL jira project and ask there.
I'm like 62% sure they will say nope. The vote process and the time for
such is to allow for PMC to review the release to give the ASF a reasonable
degree of assurance for indemnification. However, we might have a fair
degree of leeway so lo
Ok cool. It sounds like we are moving this towards a consensus? (at least
agreeing to disagree and moving forward).
I very much the different inputs on this thread - thanks for a largely
healthy discussion folks.
On Fri, Apr 10, 2020 at 6:03 AM Chris Lohfink wrote:
> I'd be in favor of going wi
So summarizing the salient points here:
- client authors have worked around this mostly, but this would avoid some
duplication of effort for new features
- this issues was tagged last year as being pertinent to 4.0 in several
threads about what was in scope
- there is some development efforts requi
hlight that feature creep is real, and hurting
> our impending release.
>
>
> On Wed, Apr 1, 2020 at 1:33 PM Nate McCall wrote:
> >
> > I think part of being a modern database is not relying on drivers/clients
> > to idiomatically rebuild the schema.
> >
> &
I think part of being a modern database is not relying on drivers/clients
to idiomatically rebuild the schema.
Thanks for bringing it up, Jon - huge +1 on merging (some form) of this.
On Thu, Apr 2, 2020 at 7:27 AM Jon Haddad wrote:
> Hey folks,
>
> I was looking through our open JIRAs and real
Given the large portion of work that's been done in EU by the Orange folks
vs. that of PST and APAC, I think this might be one for which we do two
versions: PST morning and evening.
On Wed, Apr 1, 2020 at 12:51 PM Patrick McFadin wrote:
> *Thanks for starting this thread Ben! Definitely agree th
Where was this announced? I didnt hear anything about it (it's possible I
missed an email but don't see anything).
On Sat, Mar 14, 2020 at 8:26 AM Patrick McFadin wrote:
> Hi everyone,
>
> This week, a small group of us met on Zoom on how to contribute best to the
> sidecar project (CEP-1). Data
The clash change is important to get out, but i'd like to see a few more
'moving parts' in place since most of these changes are docs. Thinking
specifically of something like CASSANDRA-15564 (repair coordinator
refactor).
I'm -0 otherwise.
On Tue, Mar 3, 2020 at 10:27 AM Jon Haddad wrote:
> Loo
[Moving to new message thread]
Thanks for bringing this up, Jordan.
IIRC, this was more a convention than a technical reason. Though I could be
completely misremembering this.
-- Forwarded message -
From: Jordan West
Date: Wed, Feb 19, 2020 at 10:13 AM
Subject: Re: 20200217 4.0
Moving to a new thread.
On Wed, Feb 19, 2020 at 10:13 AM Jordan West wrote:
> On Mon, Feb 17, 2020 at 12:52 PM Jeff Jirsa wrote:
>
> >
> > beyond the client proto change being painful for anything other than
> major
> > releases
> >
> >
> This came up during the community meeting today and I wa
+1
On Thu, Feb 13, 2020 at 4:10 PM Michael Shuler
wrote:
> +1
>
> On 2/11/20 2:36 AM, Mick Semb Wever wrote:
> >
> > Proposing the test build of Cassandra 3.0.20 for release.
> >
> > sha1: 89edf5073ba4181dd2f70294cdbcb47f5a45c82e
> > Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=s
+1
On Thu, Feb 13, 2020 at 4:10 PM Michael Shuler
wrote:
> +1
>
> On 2/10/20 2:31 PM, Mick Semb Wever wrote:
> >
> > Proposing the test build of Cassandra 2.2.16 for release.
> >
> > sha1: c4d9e9ca4ade40b956e37935bce68737b0c063b9
> > Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=s
+1
On Thu, Feb 13, 2020 at 4:10 PM Michael Shuler
wrote:
> +1
>
> On 2/11/20 2:38 AM, Mick Semb Wever wrote:
> >
> > Proposing the test build of Cassandra 3.11.6 for release.
> >
> > sha1: cb779ab9a631c13a245926f55320392c4468c6f0
> > Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=s
Good point Deepak - we do have:
http://cassandra.apache.org/doc/latest/development/dependencies.html
But we dont have details or process written down.
On Wed, Feb 12, 2020 at 9:02 AM Deepak Vohra
wrote:
>
> Dependency management is discussed at Documentation
>
> |
> |
> | |
> Documentation
>
>
Quick answer to your question though is no, it's been entirely adhoc.
On Wed, Feb 12, 2020 at 8:50 AM Nate McCall wrote:
> I would love to see an audit and rough plan on maintenance and evaluation
> criteria, etc added to the wiki for discussion. We've had a couple of users
I would love to see an audit and rough plan on maintenance and evaluation
criteria, etc added to the wiki for discussion. We've had a couple of users
complain about library versions when including the aftifact as a dependency
(even though we don't support this, a lot of people do it). It would be
c
I am delighted to share with you that we, the Apache Cassandra community,
in light of our success at last year at last year's conference, have been
given a three day track at this year's ApacheCon in New Orleans, LA, USA
[0].
The goal of this track is simple: we are going to get together to talk
a
and usability issues by providing us an isolated
> jenkins. Having our own master would simplify the setup, use and debugging,
> of Jenkins. It would still require some sunk cost but hopefully we'd end up
> with something better tailored to our needs. And with isolated agents help
>
Hi folks,
The board is looking for feedback on CI infrastructure. I'm happy to take
some (constructive) comments back. (Shuler, Mick and David Capwell
specifically as folks who've most recently wrestled with this a fair bit).
Thanks,
-Nate
-- Forwarded message -
From: Dave Fisher
>
> My .02: I think it'd improve our ability to collaborate and lower friction
> to testing if we could do so on JIRA instead of the cwiki. *I suspect *the
> edit access restrictions there plus general UX friction (difficult to have
> collab discussion, comment chains, links to things, etc) make t
+1
Thanks for getting this started, Mick!
On Fri, Jan 31, 2020 at 8:47 AM Mick Semb Wever wrote:
> Proposing the test build of Cassandra 4.0-alpha3 for release.
>
> sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/
Hello everyone,
If you have an apache.org email, you should have received an email with an
invitation to take the 2020 ASF Community Survey. Please take 15 minutes to
complete it.
If you do not have an apache.org email address and/or you didn’t receive a
link, please follow this link to the surve
Unfortunately my svn foo is about as atrophied as yours. I followed the
usual steps when publishing as I've done with the other posts, so no idea
what happened? I dont have anything uncommitted locally either.
Whatever we can do to get it showing until we move off SVN (or just move)
is fine with m
+1
On Fri, Oct 25, 2019 at 6:25 AM Michael Shuler
wrote:
> I propose the following artifacts for release as 2.2.15.
>
> sha1: 4ee4ceea28a1cb77b283c7ce0135340ddff02086
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.15-tentative
> Artifacts:
>
> https://
+1
On Fri, Oct 25, 2019 at 6:26 AM Michael Shuler
wrote:
> I propose the following artifacts for release as 3.11.5.
>
> sha1: b697af87f8e1b20d22948390d516dba1fbb9eee7
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.5-tentative
> Artifacts:
>
> https://
+1
On Fri, Oct 25, 2019 at 6:31 AM Michael Shuler
wrote:
> I propose the following artifacts for release as 3.0.19.
>
> sha1: a81bfd6b7db3a373430b3c4e8f4e930b199796f0
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.19-tentative
> Artifacts:
>
> https://
[Moved to C* only thread]
We got a lot of feedback from folks after this year's track. I'm keen to do
this again. At this point I think we are just looking at saying "yes we
would like to participate" and all details about tracks, etc. will be TBD.
Thoughts?
-Nate
-- Forwarded message -
+1
On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli wrote:
> Hi,
> We have discussed in the email thread[1] about Apache Cassandra Release
> Lifecycle. We came up with a doc[2] for it. Please vote on it if you agree
> with the content of the doc[2].
>
> Thanks,
> Sankalp
>
> [1]
>
> https://list
Hi Cyril,
Thanks for bringing this topic up. I think it would be a good idea for us
to have an "official" docker file in the source tree.
There are, however, some caveats:
https://issues.apache.org/jira/browse/LEGAL-270?focusedCommentId=15524446&page=com.atlassian.jira.plugin.system.issuetabpanels
On Fri, Aug 30, 2019 at 10:11 AM Benedict Elliott Smith
wrote:
>
> Seems to make sense to branch, right?
>
> Feels like a good line in the sand. +1
>
>
> I think the next decision is should we just cut 4.0-alpha1 now given
> that Michael has some cycles regardless of the known issues and start
> using the new fix versions for the 4.0-alpha2 release? I personally
> feel we should cut 4.0-alpha1 with every imaginable "expect this
> release to br
We can do the time mostly fair if we alternate back and forth between PST
morning and evening. This will at least let most folks attend every other
meeting.
I agree with Josh's sentiment on the discussions. We can do it, we just
have to be aware of it and defer things to Jira and/or ML.
On Thu, A
Benedict - this is totally fair ask. Initially, we wanted a wide audience
to help, but the GSoD stuff only allowed for two project contacts on the
sign up forms. Apache Airflow (the other ASF project accepted) and us both
had to do some work-arounds for how the ASF process/mail lists/etc are
setup
The topics look really interesting. Do you know if it will be recorded for
> people to catch up later?
>
> Regards
>
>
That's being discussed on the conference planning list. Unfortunately at
this point It doesnt look like they have the budget/volunteers for it this
year.
hanks,
-Nate
On Fri, Jun 7, 2019 at 11:18 AM Nate McCall wrote:
> Hi Folks,
> Thanks to everyone who submitted talks and helped out reviewing. We ended
> up with a lot more material than we could make room for, but I think we put
> together what will be a good track:
> https://www.
Hi Folks,
Thanks to everyone who submitted talks and helped out reviewing. We ended
up with a lot more material than we could make room for, but I think we put
together what will be a good track:
https://www.apachecon.com/acna19/schedule.html
If you submitted a talk and got accepted the ASF folks
gt; > > >> features and start extensive testing. Maybe its really time to
> hit>
> > > it!>
> > > > > :-)>
> > > > > >>>
> > > > > >> Attila Wind>
> > > > > >>&g
Hi Folks,
While working on ApacheCon last week, I had to get setup on ASF's slack
workspace. After poking around a bit, on a whim I created #cassandra and
#cassandra-dev. I then invited a couple of people to come signup and test
it out - primarily to make sure that the process was seamless for non-
tflix.com.INVALID> wrote:
> > >>>>
> > >>>> Having at least a ballpark target on the website will definitely
> help.
> > >> +1
> > >>>> on setting it to Q4 2019 for now.
> > >>>>
> > >>>> On Thu, May 23, 2019
Thanks for everyone to volunteered. I'll be sending out instructions later
today.
Cheers,
-Nate
On Mon, May 20, 2019 at 9:07 PM Nate McCall wrote:
> Hi Folks,
> As you probably know, the ApacheCon NA CFP recently closed. We received *a
> lot* of submissions for the Cassandra
have entire PMC vote on talks?
> > 2) We need to do t-shirts. :) Do we need corporate sponsorship for that
> > (i.e. $$)? I can look into that if so.
> >
> > On Tue, May 21, 2019 at 12:28 AM Nate McCall wrote:
> >
> >> Hi Folks,
> >> As you prob
1 - 100 of 313 matches
Mail list logo
