Got it, thanks for the correction.
On Mon, Jul 20, 2020 at 4:28 PM Brandon Williams wrote:
> I believe you can run them on 11, but you can't build them on it.
>
> On Mon, Jul 20, 2020 at 6:11 PM Jeff Jirsa wrote:
> >
> > I still dont get it, because you can't use any released version of
> >
I believe you can run them on 11, but you can't build them on it.
On Mon, Jul 20, 2020 at 6:11 PM Jeff Jirsa wrote:
>
> I still dont get it, because you can't use any released version of
> cassandra with anything other than jdk8.
>
>
>
> On Mon, Jul 20, 2020 at 2:50 PM Patrick McFadin wrote:
>
I still dont get it, because you can't use any released version of
cassandra with anything other than jdk8.
On Mon, Jul 20, 2020 at 2:50 PM Patrick McFadin wrote:
> Follow-up on the informal poll I did on twitter:
> https://twitter.com/patrickmcfadin/status/1282791302065557504?s=21
>
>
The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0-beta1.
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
Follow-up on the informal poll I did on twitter:
https://twitter.com/patrickmcfadin/status/1282791302065557504?s=21
Offered up as data to be used as you will.
161 votes
<= JDK8: 59%
JDK9 or 10: 7%
JDK11 or 12: 27%
JDK13 or 14: 7%
On Wed, Jul 15, 2020 at 3:19 AM Robert Stupp wrote:
> Yea,
> Proposing the test build of Cassandra 4.0-beta1 for release.
>
> sha1: 972da6fcffa87b3a1684362a2bab97db853372d8
> …
> The vote will be open for 60 hours (longer if needed). I've taken 12
hours off the normal 72 hours and this follows closely after the initial
4.0-beta1 vote. Everyone who has
+1
On Mon, Jul 20, 2020 at 10:58 AM Blake Eggleston
wrote:
> +1
>
> > On Jul 20, 2020, at 9:56 AM, Jon Haddad wrote:
> >
> > +1, thanks Mick for rerolling.
> >
> > On Mon, Jul 20, 2020 at 6:42 AM Joshua McKenzie
> > wrote:
> >
> >> +1
> >>
> >> On Mon, Jul 20, 2020 at 8:51 AM Jake Luciani
+1
> On Jul 20, 2020, at 9:56 AM, Jon Haddad wrote:
>
> +1, thanks Mick for rerolling.
>
> On Mon, Jul 20, 2020 at 6:42 AM Joshua McKenzie
> wrote:
>
>> +1
>>
>> On Mon, Jul 20, 2020 at 8:51 AM Jake Luciani wrote:
>>
>>> +1
>>>
>>> On Mon, Jul 20, 2020 at 8:08 AM Andrés de la Peña <
>>>
Characterizing alternate or conflicting points of view as assuming bad
intentions without justification is both unproductive and unhealthy for the
project.
> On Jul 20, 2020, at 9:14 AM, Joshua McKenzie wrote:
>
> This kind of back and forth isn't productive for the project so I'm not
>
+1, thanks Mick for rerolling.
On Mon, Jul 20, 2020 at 6:42 AM Joshua McKenzie
wrote:
> +1
>
> On Mon, Jul 20, 2020 at 8:51 AM Jake Luciani wrote:
>
> > +1
> >
> > On Mon, Jul 20, 2020 at 8:08 AM Andrés de la Peña <
> > a.penya.gar...@gmail.com>
> > wrote:
> >
> > > +1 (nb)
> > >
> > > On Mon,
I'll add in here as someone who was acting as PM on a lot of cross-team
projects at my last few gigs, this is a good example of coordination
improving the process. If people are unwilling to change their opinions or
even express them, that is an issue. Timing of release/progress is
important and
I don't think Benedict mentioned anything about people's motives or intentions,
he simply had a concern about how marketing timelines became a factor in a
release vote without the approval of the PMC. I think this is a reasonable
concern, and doesn't mean that he's assuming bad intentions.
Hi Nate,
In case this got open to contributors and not only committers, I would be
happy to assist with the activities, too.
Best regards,
Ekaterina
On Sun, 19 Jul 2020 at 17:06, Nate McCall wrote:
> >
> > Count me in. Happy to assist.
> >
> > I mean, I basically did already since you were my
Thank you, Mick, Sally et al. Appreciate this discussion.
Coordinating media releases around open source releases is not something
I've seen much of, or have much experience with. I can imagine that it is
always going to be clumsy around an organic group of individuals around the
world,
Firstly, that is a very strong claim that in this particular case is disputed
by the facts. You made a very specific claim that the delay was "risking our
currently lined up coordination with journalists and other channels". I am not
the only person to interpret this as implying coordination
> > There has been nothing about this internally at DS
>
> I would ask that you refrain from making such claims, unless you can be
> certain that you would have been privy to all such internal discussions.
Benedict, re-reading it I realised that sentence lost some important
words during my
>
> If you are criticised, it is often because of the action you took;
Actually, in this case and many others it's because of people's unfounded
assumptions about motives, incentives, and actions taken and has little to
do with reality. Which is the definition of not assuming positive intent.
On
Thanks Sally, really appreciate your insight.
To respond to the community discourse around this:
> Keep your announcement plans ... private: limit discussions to the PMC
This is all that I was asking and expecting: if somebody is making commitments
on behalf of the community (such as that a
+1
On Mon, Jul 20, 2020 at 8:51 AM Jake Luciani wrote:
> +1
>
> On Mon, Jul 20, 2020 at 8:08 AM Andrés de la Peña <
> a.penya.gar...@gmail.com>
> wrote:
>
> > +1 (nb)
> >
> > On Mon, 20 Jul 2020 at 12:58, João Reis wrote:
> >
> > > +1 (nb)
> > >
> > > The drivers smoke test suite looks good:
>
Hello everyone --Mick pinged me about this; I wanted to respond on-list for
efficacy.
We've had dozens of companies successfully help Apache Projects and their
communities help spread the word on their projects with their PR and marketing
teams. Here are some best practices:
1) Timing. Ensure
+1
On Mon, Jul 20, 2020 at 8:08 AM Andrés de la Peña
wrote:
> +1 (nb)
>
> On Mon, 20 Jul 2020 at 12:58, João Reis wrote:
>
> > +1 (nb)
> >
> > The drivers smoke test suite looks good:
> >
> >
> >
> https://ci.appveyor.com/project/DataStax/cassandra-drivers-smoke-test/builds/34194004
> >
> >
+1 (nb)
On Mon, 20 Jul 2020 at 12:58, João Reis wrote:
> +1 (nb)
>
> The drivers smoke test suite looks good:
>
>
> https://ci.appveyor.com/project/DataStax/cassandra-drivers-smoke-test/builds/34194004
>
> Mick Semb Wever escreveu no dia sábado, 18/07/2020 à(s)
> 00:27:
>
> > Proposing the
+1 (nb)
The drivers smoke test suite looks good:
https://ci.appveyor.com/project/DataStax/cassandra-drivers-smoke-test/builds/34194004
Mick Semb Wever escreveu no dia sábado, 18/07/2020 à(s)
00:27:
> Proposing the test build of Cassandra 4.0-beta1 for release.
>
> sha1:
+1 (nb)
On Sun, 19 Jul 2020 at 07:01, Ekaterina Dimitrova
wrote:
> +1(nb)
>
> On Sat, 18 Jul 2020 at 18:13, Jeff Jirsa wrote:
>
> >
> >
> > +1
> >
> > > On Jul 17, 2020, at 4:28 PM, Mick Semb Wever wrote:
> > >
> > > Proposing the test build of Cassandra 4.0-beta1 for release.
> > >
> > >
> Our plan is to share the community-approved blog with reporters who have
> expressed interest in Cassandra, which may result in coverage. We also
> developed a 4.0 beta graphic that anyone is welcome to use.
>
> FWIW our timeline revolves around yours. We're ready to reach out just as
> soon
25 matches
Mail list logo
