Re: [DISCUSS] Releases after 4.0

My preference is for a simple annual major release cadence, with minors as necessary. This is simple for the user community and developer community: support = x versions = x years. I'd like to pair this with stricter merge criteria, so that we maintain a ~shippable trunk, and we cut a release a

[DISCUSS] Releases after 4.0

Hi everybody It seems that there is a need to discuss how we will deal with releases after 4.0 We are now relatively close from the 4.0 RC release so it make sense to me to start discussing that subject especially as it has some impact on some things like dropping support for python 2 The main q

Re: [DISCUSS] When to stop supporting Python 2

While discussing with Mick in an external discussion, he raised the fact that the project approach has always been to deprecate features/support in one major version and remove them in the following one. Due to the fact that 4.0 took so long, we did not respect that approach for the Windows scripts

Re: [DISCUSS] When to stop supporting Python 2

According to some study I found here it seems that not all the organizations are ready regarding python 3. I am not a python expert. Does anybody know what are the practicalities/hurdles that users can face when upgra

Re: [DISCUSS] When to stop supporting Python 2

We have a check in CQLSH that prevents it to start if the python version is lower than python 2.7. I am fine dropping support for python 2 as long as we make it explicits in the NEWS.txt and that we add a warning in CQLSH to notify python 2 users that it is not supported anymore and might not work