We've started using the docs-impacting label <https://issues.apache.org/jira/issues/?jql=labels%20%3D%20docs-impacting%20AND%20project%20%3D%20CASSANDRA> to make it easier for the technical writers to keep up, but otherwise we're not planning any major changes.
On Thu, Jun 11, 2015 at 4:50 AM, Daniel Compton < daniel.compton.li...@gmail.com> wrote: > Hi Jonathan > > Does documentation fit into the new monthly releases and definition of > done as well, or is that part of another process? I didn't see any mention > of it in the docs, though I may have missed it. > > On Thu, 11 Jun 2015 at 9:10 pm Stefan Podkowinski < > stefan.podkowin...@1und1.de> wrote: > >> > We are also extending our backwards compatibility policy to cover all >> 3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for >> instance, including cross-version repair. >> >> What will be the EOL policy for releases after 3.0? Given your example, >> will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7? >> > -- > -- > Daniel > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
