Hi Lets put a tentative release schedule for Camel 3.x for this year, where we make it more obvious which releases are LTS and which are not.
For example having 2 yearly LTS releases and then non TLS in between allows us to innovate and move faster, but also offer production safe stable branches where end users can stay on for a longer time and get CVE and important/critical bugfixes only. Note that we should shy away from doing other fixes on these LTS branches as they are meant for "rock sold and only really important bug fixes". Not small improvements, and it would be nice to have if X can also do this etc. Lets put this kind into the non LTS releases first (when possible). A plan could be something like Camel 3.1.0 in Feb 2020 (no LTS) Camel 3.2.0 in April 2020 (no LTS) Camel 3.3.0 in June 2020 (LTS) Camel 3.4.0 in Aug 2020 (no LTS) Camel 3.5.0 in Oct 2020 (LTS) Camel 3.6.0 in Dec 2020 (no LTS) And then we do Camel 3.3.x and 3.6.x patch releases from time to time, and for about 12 months, eg 2 LTS's back, eg 3.3.x is EOL when Camel 3.9.0 LTS is released (about 1 year later). Any thoughts? -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
