Re: [VOTE] Release Apache Cassandra 3.7

[Aleksey Yeschenko]

+1

-- 
AY

On 8 June 2016 at 14:21:58, Jake Luciani (j...@apache.org) wrote:

I propose the following artifacts for release as 3.7.  

sha1: 6815dc970565e6cd1e0169b5379f37da7a5a8a32  
Git:  
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.7-tentative
  
Artifacts:  
https://repository.apache.org/content/repositories/orgapachecassandra-1116/org/apache/cassandra/apache-cassandra/3.7/
  
Staging repository:  
https://repository.apache.org/content/repositories/orgapachecassandra-1116/  

The artifacts as well as the debian package are also available here:  
http://people.apache.org/~jake  

The vote will be open for 72 hours (longer if needed).  

[1]: http://goo.gl/uA2hU1 (CHANGES.txt)  
[2]: http://goo.gl/e79k5m (NEWS.txt)  
[3]: https://goo.gl/iBt11P (Test Report)  

Re: [VOTE] Release Apache Cassandra 3.7

[Brandon Williams]

+1

On Wed, Jun 8, 2016 at 2:21 PM, Jake Luciani  wrote:

> I propose the following artifacts for release as 3.7.
>
> sha1: 6815dc970565e6cd1e0169b5379f37da7a5a8a32
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.7-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1116/org/apache/cassandra/apache-cassandra/3.7/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1116/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/uA2hU1 (CHANGES.txt)
> [2]: http://goo.gl/e79k5m (NEWS.txt)
> [3]: https://goo.gl/iBt11P (Test Report)
>

Re: [VOTE] Release Apache Cassandra 3.0.7

[Brandon Williams]

+1

On Wed, Jun 8, 2016 at 2:35 PM, Jake Luciani  wrote:

> I propose the following artifacts for release as 3.0.7.
>
> sha1: 040ac666ac5cdf9cd0a01a845f2ea0af3a81a08b
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.7-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1115/org/apache/cassandra/apache-cassandra/3.0.7/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1115/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/GYLlrI (CHANGES.txt)
> [2]: http://goo.gl/gK48Xw (NEWS.txt)
> [3]: https://goo.gl/fCrUCh (Test Report)
>

Re: [VOTE] Release Apache Cassandra 3.7

[James Carman]

On Wed, Jun 8, 2016 at 4:02 PM Sylvain Lebresne 
wrote:

>
> Because we're trying to release on a fixed cadence if possible, we're
> freezing releases for testing in advance
> so we have some time to fix problems if we find some. You can see Jake's
> email from June 6 on the freeze
> of both 3.0.7 and 3.7. That means most people already have validated/tested
> a release when the official
> vote is started.
>
>
Darn, I was hoping you guys had figured out a good way to automatically
verify releases.  I was going to borrow it for Commons :)

Thanks,

James

Re: [VOTE] Release Apache Cassandra 3.7

[Sylvain Lebresne]

On Wed, Jun 8, 2016 at 2:45 PM, James Carman 
wrote:

> How are you guys verifying these releases so fast? Do you have verification
> scripts or something?
>

Because we're trying to release on a fixed cadence if possible, we're
freezing releases for testing in advance
so we have some time to fix problems if we find some. You can see Jake's
email from June 6 on the freeze
of both 3.0.7 and 3.7. That means most people already have validated/tested
a release when the official
vote is started.


>
> On Wed, Jun 8, 2016 at 3:44 PM Jonathan Ellis  wrote:
>
> > +1
> >
> > On Wed, Jun 8, 2016 at 2:21 PM, Jake Luciani  wrote:
> >
> > > I propose the following artifacts for release as 3.7.
> > >
> > > sha1: 6815dc970565e6cd1e0169b5379f37da7a5a8a32
> > > Git:
> > >
> > >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.7-tentative
> > > Artifacts:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1116/org/apache/cassandra/apache-cassandra/3.7/
> > > Staging repository:
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1116/
> > >
> > > The artifacts as well as the debian package are also available here:
> > > http://people.apache.org/~jake
> > >
> > > The vote will be open for 72 hours (longer if needed).
> > >
> > > [1]: http://goo.gl/uA2hU1 (CHANGES.txt)
> > > [2]: http://goo.gl/e79k5m (NEWS.txt)
> > > [3]: https://goo.gl/iBt11P (Test Report)
> > >
> >
> >
> >
> > --
> > Jonathan Ellis
> > Project Chair, Apache Cassandra
> > co-founder, http://www.datastax.com
> > @spyced
> >
>

Re: [VOTE] Release Apache Cassandra 3.7

[James Carman]

How are you guys verifying these releases so fast? Do you have verification
scripts or something?

On Wed, Jun 8, 2016 at 3:44 PM Jonathan Ellis  wrote:

> +1
>
> On Wed, Jun 8, 2016 at 2:21 PM, Jake Luciani  wrote:
>
> > I propose the following artifacts for release as 3.7.
> >
> > sha1: 6815dc970565e6cd1e0169b5379f37da7a5a8a32
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.7-tentative
> > Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1116/org/apache/cassandra/apache-cassandra/3.7/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1116/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~jake
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: http://goo.gl/uA2hU1 (CHANGES.txt)
> > [2]: http://goo.gl/e79k5m (NEWS.txt)
> > [3]: https://goo.gl/iBt11P (Test Report)
> >
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder, http://www.datastax.com
> @spyced
>

Re: [VOTE] Release Apache Cassandra 3.0.7

[Sylvain Lebresne]

+1

On Wed, Jun 8, 2016 at 2:35 PM, Jake Luciani  wrote:

> I propose the following artifacts for release as 3.0.7.
>
> sha1: 040ac666ac5cdf9cd0a01a845f2ea0af3a81a08b
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.7-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1115/org/apache/cassandra/apache-cassandra/3.0.7/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1115/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/GYLlrI (CHANGES.txt)
> [2]: http://goo.gl/gK48Xw (NEWS.txt)
> [3]: https://goo.gl/fCrUCh (Test Report)
>

Re: [VOTE] Release Apache Cassandra 3.7

[Sylvain Lebresne]

+1

On Wed, Jun 8, 2016 at 2:21 PM, Jake Luciani  wrote:

> I propose the following artifacts for release as 3.7.
>
> sha1: 6815dc970565e6cd1e0169b5379f37da7a5a8a32
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.7-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1116/org/apache/cassandra/apache-cassandra/3.7/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1116/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/uA2hU1 (CHANGES.txt)
> [2]: http://goo.gl/e79k5m (NEWS.txt)
> [3]: https://goo.gl/iBt11P (Test Report)
>

[VOTE] Release Apache Cassandra 3.0.7

[Jake Luciani]

I propose the following artifacts for release as 3.0.7.

sha1: 040ac666ac5cdf9cd0a01a845f2ea0af3a81a08b
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.7-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1115/org/apache/cassandra/apache-cassandra/3.0.7/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-1115/

The artifacts as well as the debian package are also available here:
http://people.apache.org/~jake

The vote will be open for 72 hours (longer if needed).

[1]: http://goo.gl/GYLlrI (CHANGES.txt)
[2]: http://goo.gl/gK48Xw (NEWS.txt)
[3]: https://goo.gl/fCrUCh (Test Report)

[VOTE] Release Apache Cassandra 3.7

[Jake Luciani]

I propose the following artifacts for release as 3.7.

sha1: 6815dc970565e6cd1e0169b5379f37da7a5a8a32
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.7-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1116/org/apache/cassandra/apache-cassandra/3.7/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-1116/

The artifacts as well as the debian package are also available here:
http://people.apache.org/~jake

The vote will be open for 72 hours (longer if needed).

[1]: http://goo.gl/uA2hU1 (CHANGES.txt)
[2]: http://goo.gl/e79k5m (NEWS.txt)
[3]: https://goo.gl/iBt11P (Test Report)

Re: Cassandra Java Driver and DataStax

[Edward Capriolo]

What a fun topic. I re-joined the list just for this.

As I understand, it the nature of the Apache Software Licence any corporate
entity is allows to produce open and closed source software based on Apache
Cassandra, however the Cassandra name is a trademark of the ASF foundation.

As I under it, any corporation or person is free to maintain any
documentation about the software in a public or private form.

IMHO the Apache Cassandra wiki is in a sad state, and Corporate site X has
better material, but that is not an indictment of  Corporation X.

I will leave planetcassandra.org to be its own issue.

If someone were to propose a Java/Python driver to be included in the
source code of Cassandra, and said driver were rejected that would be a
clear red flag.

There are several awkward things about the driver being found at somewhere
else. These are all hypothetical but have practical implications.
Following the 'itch to scratch' philosophy perhaps I want to write the
driver in UDP for max performance. Right now even if it were implemented in
the database you have a situation where the driver living over there
ultimately is a VETO, you really can not accomplish one without there other
and they have to move lock step to do reasonable development.

There is a saying in apache something like "if it did not happen on the
list/in jira it did not happen." We have to ask ourselves honestly:

Q: Is it possible that technical writers "over there" are able to come up
with better documentation than the project itself?

A: Yes I wrote the Apache Hive book, and I believe it was more up to date
and complete than the documentation at the time

Q: Is that happening here? Who is to say?

Q: Is the CQL spec "written" in code or in documentation good enough for
someone to reasonable re-create the protocol?

Paraphrased things said on this thread that make me laugh, cry, nod:

"There are plenty of drivers like Kundera, hector"

These projects have been killed off by people as they are unable to keep up
with ever changing cassandra client specs. Thrift 0.6 -> 07 breaking
changes, CQL and the entire deprecation of thrift and the original data
model the database was built around.

"Web server X does not come with a web browser"
This is an established protocol for 20+ years and reasonable clients
already exist. That is not building a new protocol and implementation that
is conforming to an exist one apply the Apache logic to google Spdy.

"Postres does it like X"
Someone else pointed it out, but this ain't postgres, and this ain't
mongohq. The Apache licence and the Apache way are different things.

"No one at company X commits my patches because I dont work there"
As the minority (non facebook) hive committer for years I can tell you,
"wink wink"

Re: Cassandra Java Driver and DataStax

[Eric Evans]

On Sat, Jun 4, 2016 at 2:38 PM, Jonathan Ellis  wrote:
> FWIW, in very very ancient history we actually had the drivers in tree.  It
> sucked, because the people who wanted to contribute to the drivers were for
> the most part not Committers, and the committers for the most part weren't
> interested in reviewing drivers patches, and you have different,
> non-overlapping sets of contributors for each driver.  (A C++ driver author
> generally isn't very interested in clojure and vice versa.)
>
> Two things really convinced us they didn't belong in tree, even if we
> wanted to live with the above drawbacks:
>
> - If it's in tree, then the Apache committers are viewed as responsible for
> maintaining it.  Never mind if the Perl driver was (hypothetically)
> contributed by some guy who disappeared after a month and none of the
> committers know Perl, we have by committing it implicitly promised to fix
> bugs and keep it up to date with new features.
> - The obvious solution to this problem is to just not commit any driver
> that we don't have enough expertise to maintain ourselves or are not
> sufficiently confident in the author's commitment.  But then you have a
> very clear distinction between "first class," in tree drivers (probably
> just Java, maybe Python too) and everyone else, which didn't sit right with
> us either.

FWIW, at the time, I was probably one of the more vocal proponents of
this model (out-of-tree driver code), but I'm less certain these days.

First off, I think it's probably a false dichotomy to say that if we
were to admit one language that we'd be obligated to admit them all,
or that we'd be compelled to offer some arbitrary level of support for
any or all drivers simply because they are there.  We could, for
example, release a Java driver and only a Java driver because a) there
is room to share some common code with Cassandra, b) because Cassandra
is Java and the expertise is there, and c) because having one driver
is enough to serve as a reference implementation. Or we could have
some subset that met whatever objective criteria we came up with to
address concerns about supportability.  Or we could be liberal about
the drivers we accept, but conservative about the support we provide
(i.e. set realistic expectations).

One thing is as certain now as it was then, to make such a thing work,
we'd need to be far more willing to pull the trigger on new committers
than we are now.  Personally, I think we could benefit from that,
regardless of how you feel about in-tree drivers.

-- 
Eric Evans
john.eric.ev...@gmail.com

Re: Documentation

[Eric Evans]

On Tue, Jun 7, 2016 at 10:34 PM, Jonathan Ellis  wrote:
> In light of the confusion around documentation (people asking on dev list
> about driver docs or DataStax docs), I think we should accelerate the plans
> to finish migrating our official documentation from the MoinMoin wiki to
> our source tree.
>
> Briefly, the technical problems with Moin aren't going away and having the
> docs in tree means we can version them by release for free.
>
> (We still want to use a wiki for contributor-oriented pages like
> HowToContribute, but user-level docs like GettingStarted and Operations
> will be moved into tree.  And even the contributor wiki needs to move to
> Confluence  because
> MoinMoin sucks.)
>
> I've attached an outline of what I think we need to migrate to the ticket
> .

I think this is fantastic; I was completely unaware of
https://issues.apache.org/jira/browse/CASSANDRA-8700, and had been
planning to suggest exactly this.


-- 
Eric Evans
john.eric.ev...@gmail.com