+1 to semver, shippable trunk, feature flags, and better documentation about
feature support and compatibility edges - we should have a single page with a
table of version x feature, with a summary and links to detailed explanations
of everything important a user should be aware of.
I didn't re
Success of this seems predicated on keeping trunk shippable, which means
getting Harry and things like adelphi into CI/CD sooner rather than later.
I've definitely come around to Ariel's thinking about the value of having
an *actually* shippable trunk + the value of feature flags for things. It's
+1 for doing this (or something similar). It will give more clarity to
downstream users about the compatibility of a given release.
-Jeremiah
> On Apr 30, 2021, at 12:45 PM, Mick Semb Wever wrote:
>
> *** Proposal ***
> Aligned to the agreed-upon annual cadence of supported releases, let's
>
*** Proposal ***
Aligned to the agreed-upon annual cadence of supported releases, let's
use semantic versioning for better ecosystem operatibility, and to
promote API awareness and compatibility support from documentation to
tests.
*** Background ***
The recent¹ dev ML thread 'Releases after 4.0'
Hi everyone,
I have Apache Cassandra 3.11.6 with SSL encryption, CentOS Linux release
7.9, python 2.7.5. JDK and python are coming from operating system.
I have updated today operating system and with that I've got new JDK
$ java -version
openjdk version "1.8.0_292"
OpenJDK Runtime Environment (
