Re: [EXTERNAL] RE: What versions should the documentation support now?

2018-03-15 Thread Eric Evans
from the high pri emails to the user group list…) > > > > > > Sean Durity > > > > From: Kenneth Brotman [mailto:kenbrot...@yahoo.com.INVALID] > Sent: Wednesday, March 14, 2018 3:02 AM > To: user@cassandra.apache.org > Subject: [EXTERNAL] RE: What versions sh

RE: [EXTERNAL] RE: What versions should the documentation support now?

2018-03-14 Thread Kenneth Brotman
the group can manage this project when read things like that! Kenneth Brotman From: Durity, Sean R [mailto:sean_r_dur...@homedepot.com] Sent: Wednesday, March 14, 2018 12:40 PM To: user@cassandra.apache.org Subject: RE: [EXTERNAL] RE: What versions should the documentation support now

RE: [EXTERNAL] RE: What versions should the documentation support now?

2018-03-14 Thread Durity, Sean R
: Wednesday, March 14, 2018 3:02 AM To: user@cassandra.apache.org Subject: [EXTERNAL] RE: What versions should the documentation support now? Importance: High This went nowhere quick. Come on everyone. The website has to support users who are on “supported” versions of the software. That’s more

RE: What versions should the documentation support now?

2018-03-14 Thread Kenneth Brotman
[mailto:j...@jonhaddad.com] Sent: Tuesday, March 13, 2018 6:19 PM To: user@cassandra.apache.org Subject: Re: What versions should the documentation support now? Yes, I agree, we should host versioned docs. I don't think anyone is against it, it's a matter of someone having the time to do

Re: RE: RE: What versions should the documentation support now?

2018-03-14 Thread Dinesh Joshi
Dinesh Joshi [mailto:dinesh.jo...@yahoo.com.INVALID] Sent: Tuesday, March 13, 2018 11:30 PM To: user@cassandra.apache.org Subject: Re: RE: What versions should the documentation support now?   Kenneth,   The only 4.x docs should go in trunk. If you would like to contribute docs to the 2.x and/

RE: RE: What versions should the documentation support now?

2018-03-14 Thread Kenneth Brotman
I show a 3.0 and a 3.11 branch but no 4.0. I’m at https://github.com/apache/cassandra . From: Dinesh Joshi [mailto:dinesh.jo...@yahoo.com.INVALID] Sent: Tuesday, March 13, 2018 11:30 PM To: user@cassandra.apache.org Subject: Re: RE: What versions should the documentation support now

Re: RE: What versions should the documentation support now?

2018-03-14 Thread Dinesh Joshi
ll request already.   Kenneth Brotman   From: Jonathan Haddad [mailto:j...@jonhaddad.com] Sent: Tuesday, March 13, 2018 6:19 PM To: user@cassandra.apache.org Subject: Re: What versions should the documentation support now?   Yes, I agree, we should host versioned docs.  I don't think anyone

RE: What versions should the documentation support now?

2018-03-14 Thread Kenneth Brotman
...@jonhaddad.com] Sent: Tuesday, March 13, 2018 6:19 PM To: user@cassandra.apache.org Subject: Re: What versions should the documentation support now? Yes, I agree, we should host versioned docs. I don't think anyone is against it, it's a matter of someone having the time to do it. On Tue

Re: What versions should the documentation support now?

2018-03-13 Thread Jonathan Haddad
Yes, I agree, we should host versioned docs. I don't think anyone is against it, it's a matter of someone having the time to do it. On Tue, Mar 13, 2018 at 6:14 PM kurt greaves wrote: > I’ve never heard of anyone shipping docs for multiple versions, I don’t >> know why

Re: What versions should the documentation support now?

2018-03-13 Thread kurt greaves
> > I’ve never heard of anyone shipping docs for multiple versions, I don’t > know why we’d do that. You can get the docs for any version you need by > downloading C*, the docs are included. I’m a firm -1 on changing that > process. We should still host versioned docs on the website however.

Re: What versions should the documentation support now?

2018-03-12 Thread Jon Haddad
t; If we use DataStax’s example, we would have instructions for v3.0 and v2.1. >>> How’s that? >>> >>> We should have to be instructions for the cloud platforms like AWS but how >>> do you do that and stay vendor neutral? >>> >>> Kenn

RE: What versions should the documentation support now?

2018-03-12 Thread Kenneth Brotman
if we do it that way? Kenneth Brotman From: Jonathan Haddad [mailto:j...@jonhaddad.com] Sent: Monday, March 12, 2018 9:10 AM To: user@cassandra.apache.org Subject: Re: What versions should the documentation support now? Right now they can’t. On Mon, Mar 12, 2018 at 9:03 AM Kenneth

Re: What versions should the documentation support now?

2018-03-12 Thread Jonathan Haddad
; > > Kenneth Brotman > > > > *From:* Jonathan Haddad [mailto:j...@jonhaddad.com] > *Sent:* Monday, March 12, 2018 8:40 AM > > > *To:* user@cassandra.apache.org > *Subject:* Re: What versions should the documentation support now? > > > > The docs are in tree, m

RE: What versions should the documentation support now?

2018-03-12 Thread Kenneth Brotman
: Re: What versions should the documentation support now? The docs are in tree, meaning they are versioned, and should be written for the version they correspond to. Trunk docs should reflect the current state of trunk, and shouldn’t have caveats for other versions. On Mon, Mar 12, 2018 at 8

Re: What versions should the documentation support now?

2018-03-12 Thread Jonathan Haddad
> *From:* Hannu Kröger [mailto:hkro...@gmail.com] > *Sent:* Monday, March 12, 2018 7:40 AM > *To:* user@cassandra.apache.org > *Subject:* Re: What versions should the documentation support now? > > > > In my opinion, a good documentation should somehow include version &g

RE: What versions should the documentation support now?

2018-03-12 Thread Kenneth Brotman
, March 12, 2018 7:40 AM To: user@cassandra.apache.org Subject: Re: What versions should the documentation support now? In my opinion, a good documentation should somehow include version specific pieces of information. Whether it is nodetool command that came in certain version or parameter

Re: What versions should the documentation support now?

2018-03-12 Thread Hannu Kröger
In my opinion, a good documentation should somehow include version specific pieces of information. Whether it is nodetool command that came in certain version or parameter for something or something else. That would very useful. It’s confusing if I see documentation talking about 4.0 specifics

What versions should the documentation support now?

2018-03-12 Thread Kenneth Brotman
I'm unclear what versions are most popular right now? What version are you running? What version should still be supported in the documentation? For example, I'm turning my attention back to writing a section on adding a data center. What versions should I support in that information? I'm