Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Melissa Logan]

Following up on marketing contributions in process:

1. Stories have begun to post on 4.0 beta (Datanami
,
SDTimes ,
CBR
),
and we're expecting a few more from folks like The Reg, Computing (specific
to 4.0 beta), and others. We were able to secure two quotes from PMC
members, and two vendors raised their hands to speak (Instaclustr,
DataStax). We'd love to expand the bench, so please let me know if you're
available/interested for this or future efforts. The more diversity of
voices, the better.

2. With regard to community blogs, three are in process and one is in
review (with us) to see if/where to place. If you'd like to sign up, please
do so here

and
let me know if you have questions.

3. Scott Hirleman suggested on another thread

that it could be useful to create docs for marketing contributions so the
process is clear. We're happy to draft something for discussion
alongside anyone else who'd like to participate. Related: The dev list may
not be the best place to share marketing efforts on an ongoing basis, but
we want to err on the side of over-communicating for now.

Feedback welcomed and encouraged.

--Melissa

On Tue, Jul 21, 2020 at 7:20 AM Jasonstack Zhao Yang <
jasonstack.z...@gmail.com> wrote:

> sorry, my phone got unlocked accidentally in my pocket. please ignore the
> empty email.
>
> On Tue, 21 Jul 2020 at 18:40, Jasonstack Zhao Yang <
> jasonstack.z...@gmail.com> wrote:
>
> >
> > Blake Eggleston  于 2020年7月21日周二 01:57写道：
> >
> >> 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
> >> > taking this discussion further. Just want to call it out here so you
> or
> >> > others aren't left waiting for a reply.
> >> >
> >> > We can agree to disagree.
> >> >
> >> > On Mon, Jul 20, 2020 at 11:59 AM Benedict Elliott Smith <
> >> bened...@apache.org>
> >> > wrote:
> >> >
> >> >> 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 with journalists, contingent on a release schedule not
> >> agreed
> >> >> by the PMC.  This was based on semantics only; as far as I can tell,
> no
> >> >> intentions or assumptions have entered into this debate, except on
> your
> >> >> part.
> >> >>
> >> >>> Which is the definition of not assuming positive intent.
> >> >>
> >> >> Secondly, this is not the definition of positive intent.  Positive
> >> intent
> >> >> only indicates that you "mean well"
> >> >>
> >> >> Thirdly, in many recent disputes about governance, you have made a
> >> >> negative claim about my behaviour, or ascribed negative connotations
> to
> >> >> statements I have made; this is a very thinly veiled example, as I am
> >> >> clearly the object of this criticism.  I think it has reached a point
> >> where
> >> >> I can perhaps legitimately claim that you are not assuming positive
> >> intent?
> >> >>
> >> >>> motives, incentives ... little to do with reality
> >> >>
> >> >> It feels like we should return to this earlier discussion, since you
> >> >> appear to feel it is incomplete?  At the very least you seem to have
> >> taken
> >> >> the wrong message from my statements, and it is perhaps negatively
> >> >> colouring our present interactions.
> >> >>
> >> >>
> >> >> On 20/07/2020, 15:59, "Joshua McKenzie" 
> wrote:
> >> >>
> >> >>>
> >> >>> 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 Mon, Jul 20, 2020 at 10:41 AM Benedict Elliott Smith <
> >> >> bened...@apache.org>
> >> >>wrote:
> >> >>
> >> >>> 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 

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Jasonstack Zhao Yang]

Blake Eggleston  于 2020年7月21日周二 01:57写道：

> 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
> > taking this discussion further. Just want to call it out here so you or
> > others aren't left waiting for a reply.
> >
> > We can agree to disagree.
> >
> > On Mon, Jul 20, 2020 at 11:59 AM Benedict Elliott Smith <
> bened...@apache.org>
> > wrote:
> >
> >> 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 with journalists, contingent on a release schedule not
> agreed
> >> by the PMC.  This was based on semantics only; as far as I can tell, no
> >> intentions or assumptions have entered into this debate, except on your
> >> part.
> >>
> >>> Which is the definition of not assuming positive intent.
> >>
> >> Secondly, this is not the definition of positive intent.  Positive
> intent
> >> only indicates that you "mean well"
> >>
> >> Thirdly, in many recent disputes about governance, you have made a
> >> negative claim about my behaviour, or ascribed negative connotations to
> >> statements I have made; this is a very thinly veiled example, as I am
> >> clearly the object of this criticism.  I think it has reached a point
> where
> >> I can perhaps legitimately claim that you are not assuming positive
> intent?
> >>
> >>> motives, incentives ... little to do with reality
> >>
> >> It feels like we should return to this earlier discussion, since you
> >> appear to feel it is incomplete?  At the very least you seem to have
> taken
> >> the wrong message from my statements, and it is perhaps negatively
> >> colouring our present interactions.
> >>
> >>
> >> On 20/07/2020, 15:59, "Joshua McKenzie"  wrote:
> >>
> >>>
> >>> 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 Mon, Jul 20, 2020 at 10:41 AM Benedict Elliott Smith <
> >> bened...@apache.org>
> >>wrote:
> >>
> >>> 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 release can be
> >>> expected on day X), this should be coordinated with the PMC.  While
> >> it
> >>> seems to transpire that no such commitments were made, had they been
> >> made
> >>> without the knowledge of the PMC this would in my view be
> >> problematic.
> >>> This is not at all like development work, as has been alleged, since
> >> that
> >>> only takes effect after public agreement by the community.
> >>>
> >>> IMO, in general, public engagements should be run past the PMC as a
> >> final
> >>> pre-flight check regardless of any commitment being made, as the PMC
> >> should
> >>> have visibility into these activities and have the opportunity to
> >> influence
> >>> them.
> >>>
>  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.
> >>>
>  there's really no reason not to assume best intentions here
> >>>
> >>> This is a recurring taking point, that I wish we would retire except
> >> where
> >>> a clear assumption of bad faith has been made.  If you are
> >> criticised, it
> >>> is often because of the action you took; any intention you had may be
> >>> irrelevant to the criticism.  In this case, when you act on behalf
> >> of the
> >>> community, your intentions are insufficient: you must have the
> >> community's
> >>> authority to act.
> >>>
> >>>
> >>> On 20/07/2020, 14:00, "Sally Khudairi"  wrote:
> >>>
> >>>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 that the Project has announced the project
> >> milestone
> >>> first to their lists as well as announce@ before any media coverage
> >> takes
> >>> place. If 

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[Mick Semb Wever]

> 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 tested the build is invited to vote. Votes
by PMC members are considered binding. A vote passes if there are at least
three binding +1s and no -1s.
>
> Eventual publishing and announcement of the 4.0-beta1 release will be
coordinated, as described in
https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E


The vote has passed with 4 non-binding +1 vote, 7 binding +1 votes, and no
-1 votes.

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[sankalp kohli]

+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  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:
> >
> >
> >
> 
> >>>
> >>
> 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: 972da6fcffa87b3a1684362a2bab97db853372d8
> >> Git:
> >>
> >>
> >
> 
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> >> Maven Artifacts:
> >>
> >>
> >
> 
> >>>
> >>
> https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/
> >>
> >> The Source and Build Artifacts, and the Debian and RPM packages and
> >> repositories, are available here:
> >> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> >>
> >> 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 tested the build is invited to
> >> vote.
> > Votes
> >> by PMC members are considered binding. A vote passes if there are
> >> at
> > least
> >> three binding +1s and no -1s.
> >>
> >> Eventual publishing and announcement of the 4.0-beta1 release will
> >> be
> >> coordinated, as described in
> >>
> >>
> >
> 
> >>>
> >>
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> >>
> >> [1]: CHANGES.txt:
> >>
> >>
> >
> 
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> >> [2]: NEWS.txt:
> >>
> >>
> >
> 
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> >>
> >
> 
> >>>
> >>>
> >>> --
> >>> http://twitter.com/tjake
> >>>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[Blake Eggleston]

+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 <
>>> 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:
> 
> 
> 
 
>>> 
>> 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: 972da6fcffa87b3a1684362a2bab97db853372d8
>> Git:
>> 
>> 
> 
 
>>> 
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
>> Maven Artifacts:
>> 
>> 
> 
 
>>> 
>> https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/
>> 
>> The Source and Build Artifacts, and the Debian and RPM packages and
>> repositories, are available here:
>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
>> 
>> 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 tested the build is invited to
>> vote.
> Votes
>> by PMC members are considered binding. A vote passes if there are
>> at
> least
>> three binding +1s and no -1s.
>> 
>> Eventual publishing and announcement of the 4.0-beta1 release will
>> be
>> coordinated, as described in
>> 
>> 
> 
 
>>> 
>> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
>> 
>> [1]: CHANGES.txt:
>> 
>> 
> 
 
>>> 
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
>> [2]: NEWS.txt:
>> 
>> 
> 
 
>>> 
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
>> 
> 
 
>>> 
>>> 
>>> --
>>> http://twitter.com/tjake
>>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Blake Eggleston]

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
> taking this discussion further. Just want to call it out here so you or
> others aren't left waiting for a reply.
> 
> We can agree to disagree.
> 
> On Mon, Jul 20, 2020 at 11:59 AM Benedict Elliott Smith 
> wrote:
> 
>> 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 with journalists, contingent on a release schedule not agreed
>> by the PMC.  This was based on semantics only; as far as I can tell, no
>> intentions or assumptions have entered into this debate, except on your
>> part.
>> 
>>> Which is the definition of not assuming positive intent.
>> 
>> Secondly, this is not the definition of positive intent.  Positive intent
>> only indicates that you "mean well"
>> 
>> Thirdly, in many recent disputes about governance, you have made a
>> negative claim about my behaviour, or ascribed negative connotations to
>> statements I have made; this is a very thinly veiled example, as I am
>> clearly the object of this criticism.  I think it has reached a point where
>> I can perhaps legitimately claim that you are not assuming positive intent?
>> 
>>> motives, incentives ... little to do with reality
>> 
>> It feels like we should return to this earlier discussion, since you
>> appear to feel it is incomplete?  At the very least you seem to have taken
>> the wrong message from my statements, and it is perhaps negatively
>> colouring our present interactions.
>> 
>> 
>> On 20/07/2020, 15:59, "Joshua McKenzie"  wrote:
>> 
>>> 
>>> 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 Mon, Jul 20, 2020 at 10:41 AM Benedict Elliott Smith <
>> bened...@apache.org>
>>wrote:
>> 
>>> 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 release can be
>>> expected on day X), this should be coordinated with the PMC.  While
>> it
>>> seems to transpire that no such commitments were made, had they been
>> made
>>> without the knowledge of the PMC this would in my view be
>> problematic.
>>> This is not at all like development work, as has been alleged, since
>> that
>>> only takes effect after public agreement by the community.
>>> 
>>> IMO, in general, public engagements should be run past the PMC as a
>> final
>>> pre-flight check regardless of any commitment being made, as the PMC
>> should
>>> have visibility into these activities and have the opportunity to
>> influence
>>> them.
>>> 
 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.
>>> 
 there's really no reason not to assume best intentions here
>>> 
>>> This is a recurring taking point, that I wish we would retire except
>> where
>>> a clear assumption of bad faith has been made.  If you are
>> criticised, it
>>> is often because of the action you took; any intention you had may be
>>> irrelevant to the criticism.  In this case, when you act on behalf
>> of the
>>> community, your intentions are insufficient: you must have the
>> community's
>>> authority to act.
>>> 
>>> 
>>> On 20/07/2020, 14:00, "Sally Khudairi"  wrote:
>>> 
>>>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 that the Project has announced the project
>> milestone
>>> first to their lists as well as announce@ before any media coverage
>> takes
>>> place. If you're planning to time the announcements to take place in
>>> tandem, be careful with embargoes, as not everyone is able to honor
>> them.
>>> We've been burned in the past with this.
>>> 
>>>2) Messaging. Keep your announcement plans and draft press
>> releases,
>>> etc., private: limit 

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[Jon Haddad]

+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, 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 test build of Cassandra 4.0-beta1 for release.
> > > > >
> > > > > sha1: 972da6fcffa87b3a1684362a2bab97db853372d8
> > > > > Git:
> > > > >
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > > > Maven Artifacts:
> > > > >
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/
> > > > >
> > > > > The Source and Build Artifacts, and the Debian and RPM packages and
> > > > > repositories, are available here:
> > > > > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > > > >
> > > > > 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 tested the build is invited to
> vote.
> > > > Votes
> > > > > by PMC members are considered binding. A vote passes if there are
> at
> > > > least
> > > > > three binding +1s and no -1s.
> > > > >
> > > > > Eventual publishing and announcement of the 4.0-beta1 release will
> be
> > > > > coordinated, as described in
> > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > > > >
> > > > > [1]: CHANGES.txt:
> > > > >
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > > > > [2]: NEWS.txt:
> > > > >
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> > > > >
> > > >
> > >
> >
> >
> > --
> > http://twitter.com/tjake
> >
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Scott Hirleman]

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 pushing back on whether changes are necessary is valid too.

Being aware that Marketing contributions are valid/valuable community
contributions is a key to the success of a project. Seems like there were
some white spaces in what was known but this was a good resolution for all.
Is there some update to public documentation that can be put out there to
explain the coordination and timing w/ the Marketing team? Want to make
sure this isn't only included in a single email chain but is posted up for
all to review and see because it's important info.

On Fri, Jul 17, 2020 at 2:38 PM  wrote:

> Thanks for the clarification Melissa. It’s interesting to see how open
> source marketing and timing differs from “traditional”.
>
> Looks like I was mistaken about coordination implications of delay. Sorry
> for instigating needless conflict.
>
> > On Jul 17, 2020, at 5:11 PM, Mick Semb Wever  wrote:
> >
> > 
> >>
> >>
> >> The vote will be open for 72 hours (longer if needed). Everyone who has
> >> tested the build is invited to vote. Votes by PMC members are considered
> >> binding. A vote passes if there are at least three binding +1s and no
> -1s.
> >>
> >
> >
> > Vote closed/cancelled, am re-cutting it…
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

-- 
Scott Hirleman
scott.hirle...@gmail.com

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Blake Eggleston]

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. That's my reading 
at least, although maybe I missed something?

> On Jul 20, 2020, at 7:58 AM, Joshua McKenzie  wrote:
> 
>> 
>> 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 Mon, Jul 20, 2020 at 10:41 AM Benedict Elliott Smith 
> wrote:
> 
>> 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 release can be
>> expected on day X), this should be coordinated with the PMC.  While it
>> seems to transpire that no such commitments were made, had they been made
>> without the knowledge of the PMC this would in my view be problematic.
>> This is not at all like development work, as has been alleged, since that
>> only takes effect after public agreement by the community.
>> 
>> IMO, in general, public engagements should be run past the PMC as a final
>> pre-flight check regardless of any commitment being made, as the PMC should
>> have visibility into these activities and have the opportunity to influence
>> them.
>> 
>>> 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.
>> 
>>> there's really no reason not to assume best intentions here
>> 
>> This is a recurring taking point, that I wish we would retire except where
>> a clear assumption of bad faith has been made.  If you are criticised, it
>> is often because of the action you took; any intention you had may be
>> irrelevant to the criticism.  In this case, when you act on behalf of the
>> community, your intentions are insufficient: you must have the community's
>> authority to act.
>> 
>> 
>> On 20/07/2020, 14:00, "Sally Khudairi"  wrote:
>> 
>>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 that the Project has announced the project milestone
>> first to their lists as well as announce@ before any media coverage takes
>> place. If you're planning to time the announcements to take place in
>> tandem, be careful with embargoes, as not everyone is able to honor them.
>> We've been burned in the past with this.
>> 
>>2) Messaging. Keep your announcement plans and draft press releases,
>> etc., private: limit discussions to the PMC. Drafting announcements on
>> public lists, such as user@, whilst inclusive, may inadvertently expose
>> your news prematurely to the press, bloggers, and others before its ready.
>> This can be detrimental to having your news scooped before you actually
>> announce it, or conversely, having the news come out and nobody is
>> interested in covering it as it's been leaking for a while. We've also been
>> burned in the past with this. Synching messaging is also helpful to ensure
>> that the PMC speaks with a unified voice: the worst thing that can happen
>> is having someone say one thing in the media and another member of the PMC
>> saying something else, even if it's their personal opinion. Fragmentation
>> helps no-one. This recently happened with a Project on a rather
>> controversial topic, so the press was excited to see dissent within the
>> community as it gave them more to report about. Keep things co
>> ol: don't be the feature cover of a gossip tabloid.
>> 
>>3) Positioning. It's critical that whomever is speaking on behalf of
>> the Project identify themselves as such. This means that the PMC needs to
>> have a few spokespeople lined up in case of any media queries, and that the
>> spokespeople supporting the project are from different organizations so you
>> can . I cannot stress enough the need to exhibit diversity, even if
>> everyone working on the media/marketing side is from a single organization
>> --the ASF comes down hard on companies that "own" projects: we take
>> vendor-neutrality very seriously. What's worked well with organizations
>> that have pitched the press on behalf of a project is to pitch the project
>> news, have spokespeople from other organizations speak 

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Melissa Logan]

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, individuals doing their best to be independent from the companies
that employ them, companies that each have own stake in the project. We
just have to do our best! If people know of other OSS projects doing this
well it would be great to know and learn from them.
> This is a new approach for C* and our aim as a contributor is to be
transparent and follow community governance and norms. We're happy to share
what's worked marketing OSS in our experience, perhaps as an ad hoc
presentation or on an existing call -- just let me know. I've spoken to
several people in the community (from a range of companies) and everyone
shares an enthusiasm for seeing C* succeed and especially 4.0 -- from
publishing content (discussed here:
https://lists.apache.org/thread.html/r45e124f34a05dc2871cf8b094e3f57476d651933b8a69837fda0d935%40%3Cdev.cassandra.apache.org%3E)
to hosting meetups and webinars, and more.

Sally, thank you for reiterating the guidelines and will take you up on a
review of the 4.0 messaging. Will be in touch!


On Mon, Jul 20, 2020 at 8:07 AM Joshua McKenzie 
wrote:

> >
> > 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 Mon, Jul 20, 2020 at 10:41 AM Benedict Elliott Smith <
> bened...@apache.org>
> wrote:
>
> > 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 release can be
> > expected on day X), this should be coordinated with the PMC.  While it
> > seems to transpire that no such commitments were made, had they been made
> > without the knowledge of the PMC this would in my view be problematic.
> > This is not at all like development work, as has been alleged, since that
> > only takes effect after public agreement by the community.
> >
> > IMO, in general, public engagements should be run past the PMC as a final
> > pre-flight check regardless of any commitment being made, as the PMC
> should
> > have visibility into these activities and have the opportunity to
> influence
> > them.
> >
> > > 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.
> >
> > > there's really no reason not to assume best intentions here
> >
> > This is a recurring taking point, that I wish we would retire except
> where
> > a clear assumption of bad faith has been made.  If you are criticised, it
> > is often because of the action you took; any intention you had may be
> > irrelevant to the criticism.  In this case, when you act on behalf of the
> > community, your intentions are insufficient: you must have the
> community's
> > authority to act.
> >
> >
> > On 20/07/2020, 14:00, "Sally Khudairi"  wrote:
> >
> > 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 that the Project has announced the project
> milestone
> > first to their lists as well as announce@ before any media coverage
> takes
> > place. If you're planning to time the announcements to take place in
> > tandem, be careful with embargoes, as not everyone is able to honor them.
> > We've been burned in the past with this.
> >
> > 2) Messaging. Keep your announcement plans and draft press releases,
> > etc., private: limit discussions to the PMC. Drafting announcements on
> > public lists, such as user@, whilst inclusive, may inadvertently expose
> > your news prematurely to the press, bloggers, and others before its
> ready.
> > This can be detrimental to having your news scooped before you actually
> > announce it, or conversely, having the news come out and nobody is
> > interested in covering it as it's been leaking for a while. We've also
> been
> > burned in the past with this. Synching messaging is also helpful to
> ensure
> > that the PMC speaks with a unified voice: the worst thing that can happen
> > is having someone say one thing in the media and another member of the
> PMC
> > saying something else, even if 

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Benedict Elliott Smith]

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 with journalists, 
contingent on a release schedule not agreed by the PMC.  This was based on 
semantics only; as far as I can tell, no intentions or assumptions have entered 
into this debate, except on your part.

> Which is the definition of not assuming positive intent.

Secondly, this is not the definition of positive intent.  Positive intent only 
indicates that you "mean well"

Thirdly, in many recent disputes about governance, you have made a negative 
claim about my behaviour, or ascribed negative connotations to statements I 
have made; this is a very thinly veiled example, as I am clearly the object of 
this criticism.  I think it has reached a point where I can perhaps 
legitimately claim that you are not assuming positive intent?

> motives, incentives ... little to do with reality

It feels like we should return to this earlier discussion, since you appear to 
feel it is incomplete?  At the very least you seem to have taken the wrong 
message from my statements, and it is perhaps negatively colouring our present 
interactions.


On 20/07/2020, 15:59, "Joshua McKenzie"  wrote:

>
> 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 Mon, Jul 20, 2020 at 10:41 AM Benedict Elliott Smith 

wrote:

> 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 release can be
> expected on day X), this should be coordinated with the PMC.  While it
> seems to transpire that no such commitments were made, had they been made
> without the knowledge of the PMC this would in my view be problematic.
> This is not at all like development work, as has been alleged, since that
> only takes effect after public agreement by the community.
>
> IMO, in general, public engagements should be run past the PMC as a final
> pre-flight check regardless of any commitment being made, as the PMC 
should
> have visibility into these activities and have the opportunity to 
influence
> them.
>
> > 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.
>
> > there's really no reason not to assume best intentions here
>
> This is a recurring taking point, that I wish we would retire except where
> a clear assumption of bad faith has been made.  If you are criticised, it
> is often because of the action you took; any intention you had may be
> irrelevant to the criticism.  In this case, when you act on behalf of the
> community, your intentions are insufficient: you must have the community's
> authority to act.
>
>
> On 20/07/2020, 14:00, "Sally Khudairi"  wrote:
>
> 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 that the Project has announced the project milestone
> first to their lists as well as announce@ before any media coverage takes
> place. If you're planning to time the announcements to take place in
> tandem, be careful with embargoes, as not everyone is able to honor them.
> We've been burned in the past with this.
>
> 2) Messaging. Keep your announcement plans and draft press releases,
> etc., private: limit discussions to the PMC. Drafting announcements on
> public lists, such as user@, whilst inclusive, may inadvertently expose
> your news prematurely to the press, bloggers, and others before its ready.
> This can be detrimental to having your news scooped before you actually
> announce it, or conversely, having the news come out and nobody is
> interested in covering it as it's been leaking for a while. We've also 
been
> burned in the past with this. Synching messaging is also helpful to ensure
> that the PMC speaks with a unified voice: the worst thing that can 

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Mick Semb Wever]

> > 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 drafts.

*I had not seen or heard* of anything internally as DS.

I do hope everyone read and reads it as such.

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Joshua McKenzie]

>
> 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 Mon, Jul 20, 2020 at 10:41 AM Benedict Elliott Smith 
wrote:

> 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 release can be
> expected on day X), this should be coordinated with the PMC.  While it
> seems to transpire that no such commitments were made, had they been made
> without the knowledge of the PMC this would in my view be problematic.
> This is not at all like development work, as has been alleged, since that
> only takes effect after public agreement by the community.
>
> IMO, in general, public engagements should be run past the PMC as a final
> pre-flight check regardless of any commitment being made, as the PMC should
> have visibility into these activities and have the opportunity to influence
> them.
>
> > 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.
>
> > there's really no reason not to assume best intentions here
>
> This is a recurring taking point, that I wish we would retire except where
> a clear assumption of bad faith has been made.  If you are criticised, it
> is often because of the action you took; any intention you had may be
> irrelevant to the criticism.  In this case, when you act on behalf of the
> community, your intentions are insufficient: you must have the community's
> authority to act.
>
>
> On 20/07/2020, 14:00, "Sally Khudairi"  wrote:
>
> 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 that the Project has announced the project milestone
> first to their lists as well as announce@ before any media coverage takes
> place. If you're planning to time the announcements to take place in
> tandem, be careful with embargoes, as not everyone is able to honor them.
> We've been burned in the past with this.
>
> 2) Messaging. Keep your announcement plans and draft press releases,
> etc., private: limit discussions to the PMC. Drafting announcements on
> public lists, such as user@, whilst inclusive, may inadvertently expose
> your news prematurely to the press, bloggers, and others before its ready.
> This can be detrimental to having your news scooped before you actually
> announce it, or conversely, having the news come out and nobody is
> interested in covering it as it's been leaking for a while. We've also been
> burned in the past with this. Synching messaging is also helpful to ensure
> that the PMC speaks with a unified voice: the worst thing that can happen
> is having someone say one thing in the media and another member of the PMC
> saying something else, even if it's their personal opinion. Fragmentation
> helps no-one. This recently happened with a Project on a rather
> controversial topic, so the press was excited to see dissent within the
> community as it gave them more to report about. Keep things co
>  ol: don't be the feature cover of a gossip tabloid.
>
> 3) Positioning. It's critical that whomever is speaking on behalf of
> the Project identify themselves as such. This means that the PMC needs to
> have a few spokespeople lined up in case of any media queries, and that the
> spokespeople supporting the project are from different organizations so you
> can . I cannot stress enough the need to exhibit diversity, even if
> everyone working on the media/marketing side is from a single organization
> --the ASF comes down hard on companies that "own" projects: we take
> vendor-neutrality very seriously. What's worked well with organizations
> that have pitched the press on behalf of a project is to pitch the project
> news, have spokespeople from other organizations speak on behalf of the PMC
> and follow up with different spokespeople/companies that have supporting
> products or activities. The ability to showcase breadth of deployment
> demonstrates Project relevance.
>
> There have been instances of companies pre-announcing Project news and
> milestones before the Project has done so themselves, in the form of press
> releases, blog posts, articles on Medium/DZone/elsewhere, or on social
> media. Whilst we appreciate their enthusiasm, it has caused significant
> erosion 

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Benedict Elliott Smith]

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 release can be expected on day X), 
this should be coordinated with the PMC.  While it seems to transpire that no 
such commitments were made, had they been made without the knowledge of the PMC 
this would in my view be problematic.  This is not at all like development 
work, as has been alleged, since that only takes effect after public agreement 
by the community.

IMO, in general, public engagements should be run past the PMC as a final 
pre-flight check regardless of any commitment being made, as the PMC should 
have visibility into these activities and have the opportunity to influence 
them.

> 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.

> there's really no reason not to assume best intentions here

This is a recurring taking point, that I wish we would retire except where a 
clear assumption of bad faith has been made.  If you are criticised, it is 
often because of the action you took; any intention you had may be irrelevant 
to the criticism.  In this case, when you act on behalf of the community, your 
intentions are insufficient: you must have the community's authority to act.


On 20/07/2020, 14:00, "Sally Khudairi"  wrote:

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 that the Project has announced the project milestone 
first to their lists as well as announce@ before any media coverage takes 
place. If you're planning to time the announcements to take place in tandem, be 
careful with embargoes, as not everyone is able to honor them. We've been 
burned in the past with this.

2) Messaging. Keep your announcement plans and draft press releases, etc., 
private: limit discussions to the PMC. Drafting announcements on public lists, 
such as user@, whilst inclusive, may inadvertently expose your news prematurely 
to the press, bloggers, and others before its ready. This can be detrimental to 
having your news scooped before you actually announce it, or conversely, having 
the news come out and nobody is interested in covering it as it's been leaking 
for a while. We've also been burned in the past with this. Synching messaging 
is also helpful to ensure that the PMC speaks with a unified voice: the worst 
thing that can happen is having someone say one thing in the media and another 
member of the PMC saying something else, even if it's their personal opinion. 
Fragmentation helps no-one. This recently happened with a Project on a rather 
controversial topic, so the press was excited to see dissent within the 
community as it gave them more to report about. Keep things co
 ol: don't be the feature cover of a gossip tabloid.

3) Positioning. It's critical that whomever is speaking on behalf of the 
Project identify themselves as such. This means that the PMC needs to have a 
few spokespeople lined up in case of any media queries, and that the 
spokespeople supporting the project are from different organizations so you can 
. I cannot stress enough the need to exhibit diversity, even if everyone 
working on the media/marketing side is from a single organization --the ASF 
comes down hard on companies that "own" projects: we take vendor-neutrality 
very seriously. What's worked well with organizations that have pitched the 
press on behalf of a project is to pitch the project news, have spokespeople 
from other organizations speak on behalf of the PMC and follow up with 
different spokespeople/companies that have supporting products or activities. 
The ability to showcase breadth of deployment demonstrates Project relevance.

There have been instances of companies pre-announcing Project news and 
milestones before the Project has done so themselves, in the form of press 
releases, blog posts, articles on Medium/DZone/elsewhere, or on social media. 
Whilst we appreciate their enthusiasm, it has caused significant erosion of 
goodwill within the community, and issues with the press. 

Apache Projects that have been successful with outside (corporate) support 
to help with marketing and media relations have shared their press 
announcements, articles, posts, and pitches prior to going live to ensure that 
they are balanced and have proper attribution and form. I'm happy to help with 
this if needed.

Briefing analysts is a bit of a different situation, and I'm happy to 

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[Joshua McKenzie]

+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:
> > >
> > >
> > >
> >
> 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: 972da6fcffa87b3a1684362a2bab97db853372d8
> > > > Git:
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > > Maven Artifacts:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/
> > > >
> > > > The Source and Build Artifacts, and the Debian and RPM packages and
> > > > repositories, are available here:
> > > > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > > >
> > > > 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 tested the build is invited to vote.
> > > Votes
> > > > by PMC members are considered binding. A vote passes if there are at
> > > least
> > > > three binding +1s and no -1s.
> > > >
> > > > Eventual publishing and announcement of the 4.0-beta1 release will be
> > > > coordinated, as described in
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > > >
> > > > [1]: CHANGES.txt:
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > > > [2]: NEWS.txt:
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> > > >
> > >
> >
>
>
> --
> http://twitter.com/tjake
>

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Sally Khudairi]

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 that the Project has announced the project milestone first to 
their lists as well as announce@ before any media coverage takes place. If 
you're planning to time the announcements to take place in tandem, be careful 
with embargoes, as not everyone is able to honor them. We've been burned in the 
past with this.

2) Messaging. Keep your announcement plans and draft press releases, etc., 
private: limit discussions to the PMC. Drafting announcements on public lists, 
such as user@, whilst inclusive, may inadvertently expose your news prematurely 
to the press, bloggers, and others before its ready. This can be detrimental to 
having your news scooped before you actually announce it, or conversely, having 
the news come out and nobody is interested in covering it as it's been leaking 
for a while. We've also been burned in the past with this. Synching messaging 
is also helpful to ensure that the PMC speaks with a unified voice: the worst 
thing that can happen is having someone say one thing in the media and another 
member of the PMC saying something else, even if it's their personal opinion. 
Fragmentation helps no-one. This recently happened with a Project on a rather 
controversial topic, so the press was excited to see dissent within the 
community as it gave them more to report about. Keep things co
 ol: don't be the feature cover of a gossip tabloid.

3) Positioning. It's critical that whomever is speaking on behalf of the 
Project identify themselves as such. This means that the PMC needs to have a 
few spokespeople lined up in case of any media queries, and that the 
spokespeople supporting the project are from different organizations so you can 
. I cannot stress enough the need to exhibit diversity, even if everyone 
working on the media/marketing side is from a single organization --the ASF 
comes down hard on companies that "own" projects: we take vendor-neutrality 
very seriously. What's worked well with organizations that have pitched the 
press on behalf of a project is to pitch the project news, have spokespeople 
from other organizations speak on behalf of the PMC and follow up with 
different spokespeople/companies that have supporting products or activities. 
The ability to showcase breadth of deployment demonstrates Project relevance.

There have been instances of companies pre-announcing Project news and 
milestones before the Project has done so themselves, in the form of press 
releases, blog posts, articles on Medium/DZone/elsewhere, or on social media. 
Whilst we appreciate their enthusiasm, it has caused significant erosion of 
goodwill within the community, and issues with the press. 

Apache Projects that have been successful with outside (corporate) support to 
help with marketing and media relations have shared their press announcements, 
articles, posts, and pitches prior to going live to ensure that they are 
balanced and have proper attribution and form. I'm happy to help with this if 
needed.

Briefing analysts is a bit of a different situation, and I'm happy to help with 
that as well.

Best of luck,
Sally

+ forwarding to press@ as well to keep everyone in the loop

- - - 
Vice President Marketing & Publicity
Vice President Sponsor Relations
The Apache Software Foundation

Tel +1 617 921 8656 | s...@apache.org

On 2020/07/20 09:44:31, "Mick Semb Wever"  wrote: 
> 
> > 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 as the beta is cut; no need to adjust anything on our behalf. If
> > you're available for emailed or live interviews, please shoot me a note.
> > 
> > We're here to help C*. I've spoken with a handful of folks already about
> > how to best achieve that, and the door is open - reach out anytime!
> 
> 
> Thanks Melissa! If all goes well there should be a 4.0 beta release ready for 
> public this week.
> 
> 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, 
> individuals doing their best to be independent from the companies that employ 
> them, companies that each have own stake in the project. We just have to do 
> our best! If people know of other OSS projects doing this well it would be 
> great to know and learn from them.
> 
> To all non DataStax folk, I've only seen Melissa's work in this community 
> (dev and private ML). There 

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[Jake Luciani]

+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
> >
> > 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: 972da6fcffa87b3a1684362a2bab97db853372d8
> > > Git:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > Maven Artifacts:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/
> > >
> > > The Source and Build Artifacts, and the Debian and RPM packages and
> > > repositories, are available here:
> > > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > >
> > > 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 tested the build is invited to vote.
> > Votes
> > > by PMC members are considered binding. A vote passes if there are at
> > least
> > > three binding +1s and no -1s.
> > >
> > > Eventual publishing and announcement of the 4.0-beta1 release will be
> > > coordinated, as described in
> > >
> > >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > >
> > > [1]: CHANGES.txt:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > > [2]: NEWS.txt:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> > >
> >
>


-- 
http://twitter.com/tjake

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[Andrés de la Peña]

+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 test build of Cassandra 4.0-beta1 for release.
> >
> > sha1: 972da6fcffa87b3a1684362a2bab97db853372d8
> > Git:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > Maven Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/
> >
> > The Source and Build Artifacts, and the Debian and RPM packages and
> > repositories, are available here:
> > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> >
> > 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 tested the build is invited to vote.
> Votes
> > by PMC members are considered binding. A vote passes if there are at
> least
> > three binding +1s and no -1s.
> >
> > Eventual publishing and announcement of the 4.0-beta1 release will be
> > coordinated, as described in
> >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> >
> > [1]: CHANGES.txt:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > [2]: NEWS.txt:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> >
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[João Reis]

+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: 972da6fcffa87b3a1684362a2bab97db853372d8
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> Maven Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/
>
> The Source and Build Artifacts, and the Debian and RPM packages and
> repositories, are available here:
> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
>
> 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 tested the build is invited to vote. Votes
> by PMC members are considered binding. A vote passes if there are at least
> three binding +1s and no -1s.
>
> Eventual publishing and announcement of the 4.0-beta1 release will be
> coordinated, as described in
>
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
>
> [1]: CHANGES.txt:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> [2]: NEWS.txt:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[Jasonstack Zhao Yang]

+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.
> > >
> > > sha1: 972da6fcffa87b3a1684362a2bab97db853372d8
> > > Git:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > Maven Artifacts:
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/
> > >
> > > The Source and Build Artifacts, and the Debian and RPM packages and
> > > repositories, are available here:
> > > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > >
> > > 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 tested the build is invited to vote.
> > Votes
> > > by PMC members are considered binding. A vote passes if there are at
> > least
> > > three binding +1s and no -1s.
> > >
> > > Eventual publishing and announcement of the 4.0-beta1 release will be
> > > coordinated, as described in
> > >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > >
> > > [1]: CHANGES.txt:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > > [2]: NEWS.txt:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>

Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

[Mick Semb Wever]

> 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 as the beta is cut; no need to adjust anything on our behalf. If
> you're available for emailed or live interviews, please shoot me a note.
> 
> We're here to help C*. I've spoken with a handful of folks already about
> how to best achieve that, and the door is open - reach out anytime!


Thanks Melissa! If all goes well there should be a 4.0 beta release ready for 
public this week.

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, 
individuals doing their best to be independent from the companies that employ 
them, companies that each have own stake in the project. We just have to do our 
best! If people know of other OSS projects doing this well it would be great to 
know and learn from them.

To all non DataStax folk, I've only seen Melissa's work in this community (dev 
and private ML). There has been nothing about this internally at DS. The only 
thing I've heard about the media coordination is from Josh's post here, and I 
made mention of it when raising the vote: 
https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E

DS of course benefits from a successful OSS project, but so do we all, so do 
please help Melissa (and all new contributors) out, there's really no reason 
not to assume best intentions here.

regards,
Mick

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[Ekaterina Dimitrova]

+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.
> >
> > sha1: 972da6fcffa87b3a1684362a2bab97db853372d8
> > Git:
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > Maven Artifacts:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/
> >
> > The Source and Build Artifacts, and the Debian and RPM packages and
> > repositories, are available here:
> > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> >
> > 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 tested the build is invited to vote.
> Votes
> > by PMC members are considered binding. A vote passes if there are at
> least
> > three binding +1s and no -1s.
> >
> > Eventual publishing and announcement of the 4.0-beta1 release will be
> > coordinated, as described in
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> >
> > [1]: CHANGES.txt:
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > [2]: NEWS.txt:
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[Jeff Jirsa]

+1

> On Jul 17, 2020, at 4:28 PM, Mick Semb Wever  wrote:
> 
> Proposing the test build of Cassandra 4.0-beta1 for release.
> 
> sha1: 972da6fcffa87b3a1684362a2bab97db853372d8
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/
> 
> The Source and Build Artifacts, and the Debian and RPM packages and
> repositories, are available here:
> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> 
> 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 tested the build is invited to vote. Votes
> by PMC members are considered binding. A vote passes if there are at least
> three binding +1s and no -1s.
> 
> Eventual publishing and announcement of the 4.0-beta1 release will be
> coordinated, as described in
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> 
> [1]: CHANGES.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> [2]: NEWS.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

[VOTE] Release Apache Cassandra 4.0-beta1 (take2)

[Mick Semb Wever]

Proposing the test build of Cassandra 4.0-beta1 for release.

sha1: 972da6fcffa87b3a1684362a2bab97db853372d8
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1211/org/apache/cassandra/cassandra-all/4.0-beta1/

The Source and Build Artifacts, and the Debian and RPM packages and
repositories, are available here:
https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/

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 tested the build is invited to vote. Votes
by PMC members are considered binding. A vote passes if there are at least
three binding +1s and no -1s.

Eventual publishing and announcement of the 4.0-beta1 release will be
coordinated, as described in
https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E

[1]: CHANGES.txt:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
[2]: NEWS.txt:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[joshua . mckenzie]

Thanks for the clarification Melissa. It’s interesting to see how open source 
marketing and timing differs from “traditional”. 

Looks like I was mistaken about coordination implications of delay. Sorry for 
instigating needless conflict.

> On Jul 17, 2020, at 5:11 PM, Mick Semb Wever  wrote:
> 
> 
>> 
>> 
>> The vote will be open for 72 hours (longer if needed). Everyone who has
>> tested the build is invited to vote. Votes by PMC members are considered
>> binding. A vote passes if there are at least three binding +1s and no -1s.
>> 
> 
> 
> Vote closed/cancelled, am re-cutting it…

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Mick Semb Wever]

>
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s and no -1s.
>


Vote closed/cancelled, am re-cutting it…

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Melissa Logan]

Hi all, Melissa of Constantia here (just back from PTO).

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 as the beta is cut; no need to adjust anything on our behalf. If
you're available for emailed or live interviews, please shoot me a note.

We're here to help C*. I've spoken with a handful of folks already about
how to best achieve that, and the door is open - reach out anytime!

Melissa


On Fri, Jul 17, 2020 at 11:23 AM Mick Semb Wever  wrote:

> > If we agree to include this in beta-2, I'm OK with proceeding, but I
> think we'll need a separate super-majority vote on ignoring the agreed beta
> rules, which might be harder than just re-rolling the release?
>
>
> This position, on a release vote, by precedence sounds more like a -0. A
> valid concern has been raised, needs to be heard, but can and should be
> resolved within this thread and vote. It has my vote to be added to 4.0-
> beta2.
>
>
> I think it's worth pointing out that this ticket was never marked with a
> fix-version "4.0-alpha", so it was never visible as a blocker to the first
> beta release. Being strict here IMHO would mean reverting the commit and
> posting it to 4.1/5.0, rather blocking beta1.
>
> And… isn't the only thing that breaks API compatibility (and our beta
> rules)
> here is this one line:
>
> https://github.com/apache/cassandra/commit/d8993934e976d8edb94cbfe2974688dac63c5db5#diff-4805e34bd9553ede03778be66ddc06c7R268
>
>
> I can cut a new 4.0-beta1, no problems there. The bar to re-cutting a
> proposed
> release should be low enough that it's an easy enough call to request. I
> will wait a few hours before doing so, to see what eventuates here…
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Joshua McKenzie]

>
> some marketing blitz that wasn't even publicly discussed but I won't stand
> in the way.
> 2) I'm anyway very disappointed when individuals act on behalf of the
> project without involving it in the decision-making or coordination

This topic was opened on the public ML and volunteers asked for and
replied, and the pmc was engaged to review and revise the marketing blog.
We currently don't do all dev on the public ML so it's pretty consistent
with that precedent. If we want this behavior to be changed or revised (for
instance, any and all discussion or coordination for any and all individual
project contributors engaging with journalists or providing quotes about
the release), that's something we should discuss separately on another
thread.

Let's not derail this discussion further and I'd ask we be mindful about
how we characterize new contributor contributions as our community evolves.


On Fri, Jul 17, 2020 at 2:24 PM Mick Semb Wever  wrote:

> > If we agree to include this in beta-2, I'm OK with proceeding, but I
> think we'll need a separate super-majority vote on ignoring the agreed beta
> rules, which might be harder than just re-rolling the release?
>
>
> This position, on a release vote, by precedence sounds more like a -0. A
> valid concern has been raised, needs to be heard, but can and should be
> resolved within this thread and vote. It has my vote to be added to 4.0-
> beta2.
>
>
> I think it's worth pointing out that this ticket was never marked with a
> fix-version "4.0-alpha", so it was never visible as a blocker to the first
> beta release. Being strict here IMHO would mean reverting the commit and
> posting it to 4.1/5.0, rather blocking beta1.
>
> And… isn't the only thing that breaks API compatibility (and our beta
> rules)
> here is this one line:
>
> https://github.com/apache/cassandra/commit/d8993934e976d8edb94cbfe2974688dac63c5db5#diff-4805e34bd9553ede03778be66ddc06c7R268
>
>
> I can cut a new 4.0-beta1, no problems there. The bar to re-cutting a
> proposed
> release should be low enough that it's an easy enough call to request. I
> will wait a few hours before doing so, to see what eventuates here…
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Mick Semb Wever]

> If we agree to include this in beta-2, I'm OK with proceeding, but I
think we'll need a separate super-majority vote on ignoring the agreed beta
rules, which might be harder than just re-rolling the release?


This position, on a release vote, by precedence sounds more like a -0. A
valid concern has been raised, needs to be heard, but can and should be
resolved within this thread and vote. It has my vote to be added to 4.0-
beta2.


I think it's worth pointing out that this ticket was never marked with a
fix-version "4.0-alpha", so it was never visible as a blocker to the first
beta release. Being strict here IMHO would mean reverting the commit and
posting it to 4.1/5.0, rather blocking beta1.

And… isn't the only thing that breaks API compatibility (and our beta rules)
here is this one line:
https://github.com/apache/cassandra/commit/d8993934e976d8edb94cbfe2974688dac63c5db5#diff-4805e34bd9553ede03778be66ddc06c7R268


I can cut a new 4.0-beta1, no problems there. The bar to re-cutting a proposed
release should be low enough that it's an easy enough call to request. I
will wait a few hours before doing so, to see what eventuates here…

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Benedict Elliott Smith]

keting material and the ASF blog post that's lined up for
> the
> project.
>
> On Fri, Jul 17, 2020 at 5:14 AM Benedict Elliott Smith <
> bened...@apache.org>
> wrote:
>
> > -1
> >
> > Sorry, I dropped the ball on
> > https://issues.apache.org/jira/browse/CASSANDRA-15375
> >
> > It's ready to commit, if somebody can give it a quick +1, and would
> be
> > prohibited after first beta.
> >
> >
> > On 16/07/2020, 21:16, "Sumanth Pasupuleti" <
> > sumanth.pasupuleti...@gmail.com> wrote:
> >
> > +1 nb
> > Ran following CircleCI tests
> > j8_unit_tests (PASS)
> > j8_jvm_dtests (PASS)
> > j8_dtests (PASS)
> >
> > On Thu, Jul 16, 2020 at 10:18 AM Jordan West  >
> > wrote:
> >
> > > +1 nb
> > >
> > > On Thu, Jul 16, 2020 at 9:38 AM Yifan Cai 
    > > wrote:
> > >
> > > > +1 nb
> > > >
> > > > 
> > > > From: Robert Stupp 
> > > > Sent: Thursday, July 16, 2020 2:59:34 AM
> > > > To: dev@cassandra.apache.org 
> > > > Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1
> > > >
> > > > +1 (nb)
> > > >
> > > > —
> > > > Robert Stupp
> > > > @snazy
> > > >
> > > > > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang <
> > > > zhaoyangsingap...@gmail.com> wrote:
> > > > >
> > > > > +1 (nb)
> > > > >
> > > > > On Thu, 16 Jul 2020 at 01:28, Brandon Williams <
> dri...@gmail.com
> > >
> > > wrote:
> > > > >
> > > > >> +1 (binding)
> > > > >>
> > > > >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever <
> m...@apache.org>
> > wrote:
> > > > >>
> > > > >>> Proposing the test build of Cassandra 4.0-beta1 for
> release.
> > > > >>>
> > > > >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > > > >>> Git:
> > > > >>>
> > > > >>>
> > > > >>
> > > >
> > >
> >
> 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > > >>> Maven Artifacts:
> > > > >>>
> > > > >>>
> > > > >>
> > > >
> > >
> >
> 
https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> > > > >>>
> > > > >>> The Source and Build Artifacts, and the Debian and RPM
> > packages and
> > > > >>> repositories, are available here:
> > > > >>>
> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > > > >>>
> > > > >>> The vote will be open for 72 hours (longer if needed).
> > Everyone who
> > > has
> > > > >>> tested the build is invited to vote. Votes by PMC
> members are
> > > > considered
> > > > >>> binding. A vote passes if there are at least three
> binding +1s
> > and no
> > > > >> -1s.
> > > > >>>
> > > > >>> Eventual publishing and announcement of the 4.0-beta1
> release
> > will be
> > > > >>> coordinated, as described in
> > > > >>>
> > > > >>>
> > 

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Jon Haddad]

t; > wrote:
> >
> > > -1
> > >
> > > Sorry, I dropped the ball on
> > > https://issues.apache.org/jira/browse/CASSANDRA-15375
> > >
> > > It's ready to commit, if somebody can give it a quick +1, and would
> > be
> > > prohibited after first beta.
> > >
> > >
> > > On 16/07/2020, 21:16, "Sumanth Pasupuleti" <
> > > sumanth.pasupuleti...@gmail.com> wrote:
> > >
> > > +1 nb
> > > Ran following CircleCI tests
> > > j8_unit_tests (PASS)
> > > j8_jvm_dtests (PASS)
> > > j8_dtests (PASS)
> > >
> > > On Thu, Jul 16, 2020 at 10:18 AM Jordan West <
> jorda...@gmail.com
> > >
> > > wrote:
> > >
> > > > +1 nb
> > > >
> > > > On Thu, Jul 16, 2020 at 9:38 AM Yifan Cai <
> yc25c...@gmail.com>
> > > wrote:
> > > >
> > > > > +1 nb
> > > > >
> > > > > 
> > > > > From: Robert Stupp 
> > > > > Sent: Thursday, July 16, 2020 2:59:34 AM
> > > > > To: dev@cassandra.apache.org 
> > > > > Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1
> > > > >
> > > > > +1 (nb)
> > > > >
> > > > > —
> > > > > Robert Stupp
> > > > > @snazy
> > > > >
> > > > > > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang <
> > > > > zhaoyangsingap...@gmail.com> wrote:
> > > > > >
> > > > > > +1 (nb)
> > > > > >
> > > > > > On Thu, 16 Jul 2020 at 01:28, Brandon Williams <
> > dri...@gmail.com
> > > >
> > > > wrote:
> > > > > >
> > > > > >> +1 (binding)
> > > > > >>
> > > > > >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever <
> > m...@apache.org>
> > > wrote:
> > > > > >>
> > > > > >>> Proposing the test build of Cassandra 4.0-beta1 for
> > release.
> > > > > >>>
> > > > > >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > > > > >>> Git:
> > > > > >>>
> > > > > >>>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > > > >>> Maven Artifacts:
> > > > > >>>
> > > > > >>>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> > > > > >>>
> > > > > >>> The Source and Build Artifacts, and the Debian and RPM
> > > packages and
> > > > > >>> repositories, are available here:
> > > > > >>>
> > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > > > > >>>
> > > > > >>> The vote will be open for 72 hours (longer if needed).
> > > Everyone who
> > > > has
> > > > > >>> tested the build is invited to vote. Votes by PMC
> > members are
> > > > > considered
> > > > > >>> binding. A vote passes if there are at least three
> > binding +1s
> > > and no
> > > > > >> -1s.
> > > > > >>>
> > > > > >>> Eventual publishing and announcement of the 4.0-beta1
> > release
> > > will be
> > > > > >>> coordinated, as described in
> > > > > >>>
> > > > > >>>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > > > > >>>
> > > > > >>> [1]: CHANGES.txt:
> > > > > >>>
> > > > > >>>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > > > > >>> [2]: NEWS.txt:
> > > > > >>>
> > > > > >>>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> > > > > >>>
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > >
> -
> > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > For additional commands, e-mail: dev-h...@cassandra.apache.org
> > >
> > >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Benedict Elliott Smith]

> The cost to us delaying the beta over this ticket is risking our currently 
> lined up coordination with journalists and other channels

I'm not aware of any of this, except the blog post proposal?  What channels is 
this being coordinated on, and with whom?

If we agree to include this in beta-2, I'm OK with proceeding, but I think 
we'll need a separate super-majority vote on ignoring the agreed beta rules, 
which might be harder than just re-rolling the release?


On 17/07/2020, 14:42, "Joshua McKenzie"  wrote:

This -1 is due to removal of an unused, unadvertised, and likely never
working feature being removed in the config and raising an exception upon
use. Is that accurate?
>
>
I bid that we allow this into the beta and you agree to rescind your -1 as
we can reasonably conclude the likelihood of any users running into this is
basically zero. We can document it in the release notes as a known issue to
be addressed in a subsequent beta release.

The cost to us delaying the beta over this ticket is risking our currently
lined up coordination with journalists and other channels (social media,
etc) with marketing material and the ASF blog post that's lined up for the
project.

On Fri, Jul 17, 2020 at 5:14 AM Benedict Elliott Smith 
wrote:

> -1
>
> Sorry, I dropped the ball on
> https://issues.apache.org/jira/browse/CASSANDRA-15375
>
> It's ready to commit, if somebody can give it a quick +1, and would be
> prohibited after first beta.
>
>
> On 16/07/2020, 21:16, "Sumanth Pasupuleti" <
> sumanth.pasupuleti...@gmail.com> wrote:
>
> +1 nb
> Ran following CircleCI tests
> j8_unit_tests (PASS)
> j8_jvm_dtests (PASS)
> j8_dtests (PASS)
>
> On Thu, Jul 16, 2020 at 10:18 AM Jordan West 
> wrote:
>
> > +1 nb
> >
> > On Thu, Jul 16, 2020 at 9:38 AM Yifan Cai 
> wrote:
> >
> > > +1 nb
> > >
> > > 
>     > > From: Robert Stupp 
    > > > Sent: Thursday, July 16, 2020 2:59:34 AM
> > > To: dev@cassandra.apache.org 
> > > Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1
> > >
> > > +1 (nb)
> > >
> > > —
> > > Robert Stupp
> > > @snazy
> > >
> > > > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang <
> > > zhaoyangsingap...@gmail.com> wrote:
> > > >
> > > > +1 (nb)
> > > >
> > > > On Thu, 16 Jul 2020 at 01:28, Brandon Williams  >
> > wrote:
> > > >
> > > >> +1 (binding)
> > > >>
> > > >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever 
> wrote:
> > > >>
> > > >>> Proposing the test build of Cassandra 4.0-beta1 for release.
> > > >>>
> > > >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > > >>> Git:
> > > >>>
> > > >>>
> > > >>
> > >
> >
> 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > >>> Maven Artifacts:
> > > >>>
> > > >>>
> > > >>
> > >
> >
> 
https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> > > >>>
> > > >>> The Source and Build Artifacts, and the Debian and RPM
> packages and
> > > >>> repositories, are available here:
> > > >>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > > >>>
> > > >>> The vote will be open for 72 hours (longer if needed).
> Everyone who
> > has
> > > >>> tested the build is invited to vote. Votes by PMC members are
> > > considered
> > > >>> binding. A vote passes if there are at least three binding +1s
> and no
> > > >> -1s.
> > > >&

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Joshua McKenzie]

This -1 is due to removal of an unused, unadvertised, and likely never
working feature being removed in the config and raising an exception upon
use. Is that accurate?
>
>
I bid that we allow this into the beta and you agree to rescind your -1 as
we can reasonably conclude the likelihood of any users running into this is
basically zero. We can document it in the release notes as a known issue to
be addressed in a subsequent beta release.

The cost to us delaying the beta over this ticket is risking our currently
lined up coordination with journalists and other channels (social media,
etc) with marketing material and the ASF blog post that's lined up for the
project.

On Fri, Jul 17, 2020 at 5:14 AM Benedict Elliott Smith 
wrote:

> -1
>
> Sorry, I dropped the ball on
> https://issues.apache.org/jira/browse/CASSANDRA-15375
>
> It's ready to commit, if somebody can give it a quick +1, and would be
> prohibited after first beta.
>
>
> On 16/07/2020, 21:16, "Sumanth Pasupuleti" <
> sumanth.pasupuleti...@gmail.com> wrote:
>
> +1 nb
> Ran following CircleCI tests
> j8_unit_tests (PASS)
> j8_jvm_dtests (PASS)
> j8_dtests (PASS)
>
> On Thu, Jul 16, 2020 at 10:18 AM Jordan West 
> wrote:
>
> > +1 nb
> >
> > On Thu, Jul 16, 2020 at 9:38 AM Yifan Cai 
> wrote:
> >
> > > +1 nb
> > >
> > > 
>     > > From: Robert Stupp 
>     > > Sent: Thursday, July 16, 2020 2:59:34 AM
> > > To: dev@cassandra.apache.org 
> > > Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1
> > >
> > > +1 (nb)
> > >
> > > —
> > > Robert Stupp
> > > @snazy
> > >
> > > > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang <
> > > zhaoyangsingap...@gmail.com> wrote:
> > > >
> > > > +1 (nb)
> > > >
> > > > On Thu, 16 Jul 2020 at 01:28, Brandon Williams  >
> > wrote:
> > > >
> > > >> +1 (binding)
> > > >>
> > > >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever 
> wrote:
> > > >>
> > > >>> Proposing the test build of Cassandra 4.0-beta1 for release.
> > > >>>
> > > >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > > >>> Git:
> > > >>>
> > > >>>
> > > >>
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > >>> Maven Artifacts:
> > > >>>
> > > >>>
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> > > >>>
> > > >>> The Source and Build Artifacts, and the Debian and RPM
> packages and
> > > >>> repositories, are available here:
> > > >>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > > >>>
> > > >>> The vote will be open for 72 hours (longer if needed).
> Everyone who
> > has
> > > >>> tested the build is invited to vote. Votes by PMC members are
> > > considered
> > > >>> binding. A vote passes if there are at least three binding +1s
> and no
> > > >> -1s.
> > > >>>
> > > >>> Eventual publishing and announcement of the 4.0-beta1 release
> will be
> > > >>> coordinated, as described in
> > > >>>
> > > >>>
> > > >>
> > >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > > >>>
> > > >>> [1]: CHANGES.txt:
> > > >>>
> > > >>>
> > > >>
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > > >>> [2]: NEWS.txt:
> > > >>>
> > > >>>
> > > >>
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> > > >>>
> > > >>
> > >
> > >
> >
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Benedict Elliott Smith]

-1

Sorry, I dropped the ball on 
https://issues.apache.org/jira/browse/CASSANDRA-15375

It's ready to commit, if somebody can give it a quick +1, and would be 
prohibited after first beta.


On 16/07/2020, 21:16, "Sumanth Pasupuleti"  
wrote:

+1 nb
Ran following CircleCI tests
j8_unit_tests (PASS)
j8_jvm_dtests (PASS)
j8_dtests (PASS)

On Thu, Jul 16, 2020 at 10:18 AM Jordan West  wrote:

> +1 nb
>
> On Thu, Jul 16, 2020 at 9:38 AM Yifan Cai  wrote:
>
> > +1 nb
> >
> > 
> > From: Robert Stupp 
> > Sent: Thursday, July 16, 2020 2:59:34 AM
> > To: dev@cassandra.apache.org 
> > Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1
> >
> > +1 (nb)
> >
> > —
> > Robert Stupp
> > @snazy
> >
> > > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang <
> > zhaoyangsingap...@gmail.com> wrote:
> > >
> > > +1 (nb)
> > >
> > > On Thu, 16 Jul 2020 at 01:28, Brandon Williams 
> wrote:
> > >
> > >> +1 (binding)
> > >>
> > >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever  
wrote:
> > >>
> > >>> Proposing the test build of Cassandra 4.0-beta1 for release.
> > >>>
> > >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > >>> Git:
> > >>>
> > >>>
> > >>
> >
> 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > >>> Maven Artifacts:
> > >>>
> > >>>
> > >>
> >
> 
https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> > >>>
> > >>> The Source and Build Artifacts, and the Debian and RPM packages and
> > >>> repositories, are available here:
> > >>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > >>>
> > >>> The vote will be open for 72 hours (longer if needed). Everyone who
> has
> > >>> tested the build is invited to vote. Votes by PMC members are
> > considered
> > >>> binding. A vote passes if there are at least three binding +1s and 
no
> > >> -1s.
> > >>>
> > >>> Eventual publishing and announcement of the 4.0-beta1 release will 
be
> > >>> coordinated, as described in
> > >>>
> > >>>
> > >>
> >
> 
https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > >>>
> > >>> [1]: CHANGES.txt:
> > >>>
> > >>>
> > >>
> >
> 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > >>> [2]: NEWS.txt:
> > >>>
> > >>>
> > >>
> >
> 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> > >>>
> > >>
> >
> >
>



-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Sumanth Pasupuleti]

+1 nb
Ran following CircleCI tests
j8_unit_tests (PASS)
j8_jvm_dtests (PASS)
j8_dtests (PASS)

On Thu, Jul 16, 2020 at 10:18 AM Jordan West  wrote:

> +1 nb
>
> On Thu, Jul 16, 2020 at 9:38 AM Yifan Cai  wrote:
>
> > +1 nb
> >
> > 
> > From: Robert Stupp 
> > Sent: Thursday, July 16, 2020 2:59:34 AM
> > To: dev@cassandra.apache.org 
> > Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1
> >
> > +1 (nb)
> >
> > —
> > Robert Stupp
> > @snazy
> >
> > > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang <
> > zhaoyangsingap...@gmail.com> wrote:
> > >
> > > +1 (nb)
> > >
> > > On Thu, 16 Jul 2020 at 01:28, Brandon Williams 
> wrote:
> > >
> > >> +1 (binding)
> > >>
> > >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever  wrote:
> > >>
> > >>> Proposing the test build of Cassandra 4.0-beta1 for release.
> > >>>
> > >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > >>> Git:
> > >>>
> > >>>
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > >>> Maven Artifacts:
> > >>>
> > >>>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> > >>>
> > >>> The Source and Build Artifacts, and the Debian and RPM packages and
> > >>> repositories, are available here:
> > >>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > >>>
> > >>> The vote will be open for 72 hours (longer if needed). Everyone who
> has
> > >>> tested the build is invited to vote. Votes by PMC members are
> > considered
> > >>> binding. A vote passes if there are at least three binding +1s and no
> > >> -1s.
> > >>>
> > >>> Eventual publishing and announcement of the 4.0-beta1 release will be
> > >>> coordinated, as described in
> > >>>
> > >>>
> > >>
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > >>>
> > >>> [1]: CHANGES.txt:
> > >>>
> > >>>
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > >>> [2]: NEWS.txt:
> > >>>
> > >>>
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> > >>>
> > >>
> >
> >
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Jordan West]

+1 nb

On Thu, Jul 16, 2020 at 9:38 AM Yifan Cai  wrote:

> +1 nb
>
> 
> From: Robert Stupp 
> Sent: Thursday, July 16, 2020 2:59:34 AM
> To: dev@cassandra.apache.org 
> Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1
>
> +1 (nb)
>
> —
> Robert Stupp
> @snazy
>
> > On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang <
> zhaoyangsingap...@gmail.com> wrote:
> >
> > +1 (nb)
> >
> > On Thu, 16 Jul 2020 at 01:28, Brandon Williams  wrote:
> >
> >> +1 (binding)
> >>
> >> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever  wrote:
> >>
> >>> Proposing the test build of Cassandra 4.0-beta1 for release.
> >>>
> >>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> >>> Git:
> >>>
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> >>> Maven Artifacts:
> >>>
> >>>
> >>
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> >>>
> >>> The Source and Build Artifacts, and the Debian and RPM packages and
> >>> repositories, are available here:
> >>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> >>>
> >>> The vote will be open for 72 hours (longer if needed). Everyone who has
> >>> tested the build is invited to vote. Votes by PMC members are
> considered
> >>> binding. A vote passes if there are at least three binding +1s and no
> >> -1s.
> >>>
> >>> Eventual publishing and announcement of the 4.0-beta1 release will be
> >>> coordinated, as described in
> >>>
> >>>
> >>
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> >>>
> >>> [1]: CHANGES.txt:
> >>>
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> >>> [2]: NEWS.txt:
> >>>
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> >>>
> >>
>
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Yifan Cai]

+1 nb


From: Robert Stupp 
Sent: Thursday, July 16, 2020 2:59:34 AM
To: dev@cassandra.apache.org 
Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1

+1 (nb)

—
Robert Stupp
@snazy

> On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang  
> wrote:
>
> +1 (nb)
>
> On Thu, 16 Jul 2020 at 01:28, Brandon Williams  wrote:
>
>> +1 (binding)
>>
>> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever  wrote:
>>
>>> Proposing the test build of Cassandra 4.0-beta1 for release.
>>>
>>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
>>> Git:
>>>
>>>
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
>>> Maven Artifacts:
>>>
>>>
>> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
>>>
>>> The Source and Build Artifacts, and the Debian and RPM packages and
>>> repositories, are available here:
>>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
>>>
>>> The vote will be open for 72 hours (longer if needed). Everyone who has
>>> tested the build is invited to vote. Votes by PMC members are considered
>>> binding. A vote passes if there are at least three binding +1s and no
>> -1s.
>>>
>>> Eventual publishing and announcement of the 4.0-beta1 release will be
>>> coordinated, as described in
>>>
>>>
>> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
>>>
>>> [1]: CHANGES.txt:
>>>
>>>
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
>>> [2]: NEWS.txt:
>>>
>>>
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
>>>
>>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Robert Stupp]

+1 (nb)

—
Robert Stupp
@snazy

> On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang  
> wrote:
> 
> +1 (nb)
> 
> On Thu, 16 Jul 2020 at 01:28, Brandon Williams  wrote:
> 
>> +1 (binding)
>> 
>> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever  wrote:
>> 
>>> Proposing the test build of Cassandra 4.0-beta1 for release.
>>> 
>>> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
>>> Git:
>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
>>> Maven Artifacts:
>>> 
>>> 
>> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
>>> 
>>> The Source and Build Artifacts, and the Debian and RPM packages and
>>> repositories, are available here:
>>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
>>> 
>>> The vote will be open for 72 hours (longer if needed). Everyone who has
>>> tested the build is invited to vote. Votes by PMC members are considered
>>> binding. A vote passes if there are at least three binding +1s and no
>> -1s.
>>> 
>>> Eventual publishing and announcement of the 4.0-beta1 release will be
>>> coordinated, as described in
>>> 
>>> 
>> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
>>> 
>>> [1]: CHANGES.txt:
>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
>>> [2]: NEWS.txt:
>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
>>> 
>> 

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Jasonstack Zhao Yang]

+1 (nb)

On Thu, 16 Jul 2020 at 01:28, Brandon Williams  wrote:

> +1 (binding)
>
> On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever  wrote:
>
> > Proposing the test build of Cassandra 4.0-beta1 for release.
> >
> > sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > Git:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > Maven Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> >
> > The Source and Build Artifacts, and the Debian and RPM packages and
> > repositories, are available here:
> > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> >
> > The vote will be open for 72 hours (longer if needed). Everyone who has
> > tested the build is invited to vote. Votes by PMC members are considered
> > binding. A vote passes if there are at least three binding +1s and no
> -1s.
> >
> > Eventual publishing and announcement of the 4.0-beta1 release will be
> > coordinated, as described in
> >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> >
> > [1]: CHANGES.txt:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > [2]: NEWS.txt:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> >
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Brandon Williams]

+1 (binding)

On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever  wrote:

> Proposing the test build of Cassandra 4.0-beta1 for release.
>
> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> Maven Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
>
> The Source and Build Artifacts, and the Debian and RPM packages and
> repositories, are available here:
> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
>
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s and no -1s.
>
> Eventual publishing and announcement of the 4.0-beta1 release will be
> coordinated, as described in
>
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
>
> [1]: CHANGES.txt:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> [2]: NEWS.txt:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Andrés de la Peña]

+1 (non-binding)

On Wed, 15 Jul 2020 at 16:53, Jake Luciani  wrote:

> +1 (binding)
>
> On Wed, Jul 15, 2020 at 11:50 AM Joshua McKenzie 
> wrote:
>
> > +1 (binding)
> >
> > On Wed, Jul 15, 2020 at 3:33 AM Yuji Ito  wrote:
> >
> > > +1 (non-binding)
> > >
> > > Short Jepsen tests with crash injection for map, set, counter, batch,
> and
> > > LWT passed.
> > > https://github.com/scalar-labs/scalar-jepsen
> > >
> > > 2020年7月15日(水) 8:06 Mick Semb Wever :
> > >
> > > > Proposing the test build of Cassandra 4.0-beta1 for release.
> > > >
> > > > sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > > > Git:
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > > Maven Artifacts:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> > > >
> > > > The Source and Build Artifacts, and the Debian and RPM packages and
> > > > repositories, are available here:
> > > > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > > >
> > > > The vote will be open for 72 hours (longer if needed). Everyone who
> has
> > > > tested the build is invited to vote. Votes by PMC members are
> > considered
> > > > binding. A vote passes if there are at least three binding +1s and no
> > > -1s.
> > > >
> > > > Eventual publishing and announcement of the 4.0-beta1 release will be
> > > > coordinated, as described in
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > > >
> > > > [1]: CHANGES.txt:
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > > > [2]: NEWS.txt:
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> > > >
> > >
> >
>
>
> --
> http://twitter.com/tjake
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Ekaterina Dimitrova]

+1 (non-binding)

On Wed, 15 Jul 2020 at 11:50, Joshua McKenzie  wrote:

> +1 (binding)
>
> On Wed, Jul 15, 2020 at 3:33 AM Yuji Ito  wrote:
>
> > +1 (non-binding)
> >
> > Short Jepsen tests with crash injection for map, set, counter, batch, and
> > LWT passed.
> > https://github.com/scalar-labs/scalar-jepsen
> >
> > 2020年7月15日(水) 8:06 Mick Semb Wever :
> >
> > > Proposing the test build of Cassandra 4.0-beta1 for release.
> > >
> > > sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > > Git:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > Maven Artifacts:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> > >
> > > The Source and Build Artifacts, and the Debian and RPM packages and
> > > repositories, are available here:
> > > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > >
> > > The vote will be open for 72 hours (longer if needed). Everyone who has
> > > tested the build is invited to vote. Votes by PMC members are
> considered
> > > binding. A vote passes if there are at least three binding +1s and no
> > -1s.
> > >
> > > Eventual publishing and announcement of the 4.0-beta1 release will be
> > > coordinated, as described in
> > >
> > >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > >
> > > [1]: CHANGES.txt:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > > [2]: NEWS.txt:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> > >
> >
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Jake Luciani]

+1 (binding)

On Wed, Jul 15, 2020 at 11:50 AM Joshua McKenzie 
wrote:

> +1 (binding)
>
> On Wed, Jul 15, 2020 at 3:33 AM Yuji Ito  wrote:
>
> > +1 (non-binding)
> >
> > Short Jepsen tests with crash injection for map, set, counter, batch, and
> > LWT passed.
> > https://github.com/scalar-labs/scalar-jepsen
> >
> > 2020年7月15日(水) 8:06 Mick Semb Wever :
> >
> > > Proposing the test build of Cassandra 4.0-beta1 for release.
> > >
> > > sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > > Git:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > > Maven Artifacts:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> > >
> > > The Source and Build Artifacts, and the Debian and RPM packages and
> > > repositories, are available here:
> > > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> > >
> > > The vote will be open for 72 hours (longer if needed). Everyone who has
> > > tested the build is invited to vote. Votes by PMC members are
> considered
> > > binding. A vote passes if there are at least three binding +1s and no
> > -1s.
> > >
> > > Eventual publishing and announcement of the 4.0-beta1 release will be
> > > coordinated, as described in
> > >
> > >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> > >
> > > [1]: CHANGES.txt:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > > [2]: NEWS.txt:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> > >
> >
>


-- 
http://twitter.com/tjake

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Joshua McKenzie]

+1 (binding)

On Wed, Jul 15, 2020 at 3:33 AM Yuji Ito  wrote:

> +1 (non-binding)
>
> Short Jepsen tests with crash injection for map, set, counter, batch, and
> LWT passed.
> https://github.com/scalar-labs/scalar-jepsen
>
> 2020年7月15日(水) 8:06 Mick Semb Wever :
>
> > Proposing the test build of Cassandra 4.0-beta1 for release.
> >
> > sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> > Git:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> > Maven Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
> >
> > The Source and Build Artifacts, and the Debian and RPM packages and
> > repositories, are available here:
> > https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
> >
> > The vote will be open for 72 hours (longer if needed). Everyone who has
> > tested the build is invited to vote. Votes by PMC members are considered
> > binding. A vote passes if there are at least three binding +1s and no
> -1s.
> >
> > Eventual publishing and announcement of the 4.0-beta1 release will be
> > coordinated, as described in
> >
> >
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
> >
> > [1]: CHANGES.txt:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> > [2]: NEWS.txt:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
> >
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[João Reis]

 +1 (non-binding)

I've run the drivers smoke test suite and build jobs look good (there's 1
test failure that is not related to the server build):

https://ci.appveyor.com/project/DataStax/cassandra-drivers-smoke-test/builds/34108936

Mick Semb Wever  escreveu no dia quarta, 15/07/2020 à(s)
00:06:

> Proposing the test build of Cassandra 4.0-beta1 for release.
>
> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> Maven Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
>
> The Source and Build Artifacts, and the Debian and RPM packages and
> repositories, are available here:
> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
>
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s and no -1s.
>
> Eventual publishing and announcement of the 4.0-beta1 release will be
> coordinated, as described in
>
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
>
> [1]: CHANGES.txt:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> [2]: NEWS.txt:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
>

Re: [VOTE] Release Apache Cassandra 4.0-beta1

[Yuji Ito]

+1 (non-binding)

Short Jepsen tests with crash injection for map, set, counter, batch, and
LWT passed.
https://github.com/scalar-labs/scalar-jepsen

2020年7月15日(水) 8:06 Mick Semb Wever :

> Proposing the test build of Cassandra 4.0-beta1 for release.
>
> sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
> Git:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
> Maven Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/
>
> The Source and Build Artifacts, and the Debian and RPM packages and
> repositories, are available here:
> https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/
>
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s and no -1s.
>
> Eventual publishing and announcement of the 4.0-beta1 release will be
> coordinated, as described in
>
> https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E
>
> [1]: CHANGES.txt:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
> [2]: NEWS.txt:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative
>

[VOTE] Release Apache Cassandra 4.0-beta1

[Mick Semb Wever]

Proposing the test build of Cassandra 4.0-beta1 for release.

sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1210/org/apache/cassandra/cassandra-all/4.0-beta1/

The Source and Build Artifacts, and the Debian and RPM packages and
repositories, are available here:
https://dist.apache.org/repos/dist/dev/cassandra/4.0-beta1/

The vote will be open for 72 hours (longer if needed). Everyone who has
tested the build is invited to vote. Votes by PMC members are considered
binding. A vote passes if there are at least three binding +1s and no -1s.

Eventual publishing and announcement of the 4.0-beta1 release will be
coordinated, as described in
https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E

[1]: CHANGES.txt:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-beta1-tentative
[2]: NEWS.txt:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-beta1-tentative