[camel-website] branch schedule created (now 324b9eb)

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a change to branch schedule
in repository https://gitbox.apache.org/repos/asf/camel-website.git.


      at 324b9eb  Blog post about LTS and release schedule

This branch includes the following new commits:

     new 324b9eb  Blog post about LTS and release schedule

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[camel-website] 01/01: Blog post about LTS and release schedule

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch schedule
in repository https://gitbox.apache.org/repos/asf/camel-website.git

commit 324b9ebc149b9d8d631676d7283e4f3f34f798b9
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Fri Mar 6 10:12:48 2020 +0100

    Blog post about LTS and release schedule
---
 content/blog/LTS-Release-Schedule/index.md | 57 ++++++++++++++++++++++++++++++
 1 file changed, 57 insertions(+)

diff --git a/content/blog/LTS-Release-Schedule/index.md b/content/blog/LTS-Release-Schedule/index.md
new file mode 100644
index 0000000..ead9d1f
--- /dev/null
+++ b/content/blog/LTS-Release-Schedule/index.md
@@ -0,0 +1,57 @@
+---
+title: "Apache Camel 2020 Release Schedule"
+date: 2020-3-6
+author: Claus Ibsen
+categories: ["Roadmap"]
+preview: Apache Camel 2020 Release Schedule
+---
+
+The Apache Camel project is moving to release schedule with LTS (Long Term Support) and non-LTS releases.
+
+The plan is to have 2 yearly LTS releases and then non-LTS releases in between.
+
+This allows the Camel project to innovate and move much faster (non-LTS).
+
+And as well to offer production stable branches (LTS) where end users can stay on
+for a longer period of time and get CVEs and important/critical bug fixes only.
+On these LTS branches we plan to avoid introducing new features, improvements etc, and
+keep changes with production in-mind only. However exceptions can be made.
+
+For non-LTS releases then we plan to not release patch releases, for example there will
+not be 3.1.1, 3.1.2 patch releases for the non-LTS release of Camel 3.1.0.
+
+Other projects like Java JDK has moved to LTS and non-TLS releases as well. So we are doing the same,
+but our LTS is limited to 1-year schedule (typically same timeframe for Camel 2.x).
+
+## Release Schedule
+
+The tentative release schedule for 2020 is as follows:
+
+| Release | Date | LTS | EOL | Java | 
+|---------|------|-----|-----|------|
+| 3.1.0 | Feb 2020 | No |  | 8, 11 |
+| 3.2.0 | Apr 2020 | No |  | 8, 11 |
+| 3.3.0 | Jun 2020 | Yes | Jun 2021 | 8, 11 |
+| 3.4.0 | Aug 2020 | No | | 11 |
+| 3.5.0 | Oct 2020 | No | | 11 | 
+| 3.6.0 | Dec 2020 | Yes | Dec 2021 | 11 |
+
+NOTE: The schedule is tentative and subject for change
+(for example date's may slip into the following month). 
+
+So for 2020 we have planned 2 LTS releases, Camel 3.3.x and 3.6.x where we will release
+patch releases. The LTS releases are generally supported for 1-year
+(latest 2 LTS releases are active supported)
+
+For each Camel release we will clearly mark in the release notes whether its a LTS or non-LTS release.
+
+## Java 8 and 11
+
+Java 8 is planned to be dropped after the first Camel 3 LTS release (currently
+planned as Camel 3.3). 
+
+Java 8 was originally intended to be dropped entirely for Camel 3,
+but we wanted to allow end users to migrate from Camel 2.x to 3.x without having
+to also upgrade from Java 8 to 11 at the same time. So this means that users
+can safely migrate from Camel 2.x to Camel 3.3.x and stay on Java 8 and have this supported
+until June 2021. But we encourage Camel users to move to Java 11 when possible.