You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/03/06 09:38:10 UTC

[GitHub] [camel-website] davsclaus opened a new pull request #166: Blog post about LTS and release schedule

davsclaus opened a new pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166
 
 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on issue #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on issue #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#issuecomment-595722532
 
 
   I've pushed a commit (2d199d5ea3cf3fc8399b8f806d22a2f333b13830) to add a featured image and fix the table formatting.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] oscerd commented on issue #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

oscerd commented on issue #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#issuecomment-595760725
 
 
   +1

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388808086

##########
File path: 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.

Review comment:
```suggestion
keep changes with production in-mind only. However, exceptions can be made.
```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388810031
 
 

 ##########
 File path: 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.
 
 Review comment:
   ```suggestion
   For each Camel release, we will mark in the release notes whether its a LTS or non-LTS release.
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388808932

Review comment:
```suggestion
Other projects like Java JDK have moved to LTS and non-TLS releases as well. So we are doing the same,
```

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on issue #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on issue #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#issuecomment-595717032
 
 
   Preview is [here](https://builds.apache.org/job/Camel.website/job/PR-166/Preview/blog/LTS-Release-Schedule/).
   
   The markdown tables seem to render incorrectly. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart merged pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart merged pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166
 
 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388809329
 
 

 ##########
 File path: 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
 
 Review comment:
   ```suggestion
   So for 2020, we have planned 2 LTS releases, Camel 3.3.x and 3.6.x where we will release
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on issue #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on issue #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#issuecomment-595736146
 
 
   The preview with those changes is [here](https://builds.apache.org/job/Camel.website/job/PR-166/Preview/blog/LTS-Release-Schedule/) (same URL).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388807965
 
 

 ##########
 File path: 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
 
 Review comment:
   ```suggestion
   On these LTS branches, we plan to avoid introducing new features, improvements etc, and
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388806331
 
 

 ##########
 File path: content/blog/LTS-Release-Schedule/index.md
 ##########
 @@ -0,0 +1,57 @@
+---
+title: "Apache Camel 2020 Release Schedule"
+date: 2020-3-6
 
 Review comment:
   Not 100% sure about the date format, it might require this:
   
   ```suggestion
   date: 2020-03-06
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388809433
 
 

 ##########
 File path: 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)
 
 Review comment:
   ```suggestion
   (latest 2 LTS releases are actively supported)
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388806009
 
 

 ##########
 File path: content/blog/LTS-Release-Schedule/index.md
 ##########
 @@ -0,0 +1,57 @@
+---
+title: "Apache Camel 2020 Release Schedule"
+date: 2020-3-6
+author: Claus Ibsen
 
 Review comment:
   To get the blog post published we need `draft: false` in the front matter
   ```suggestion
   author: Claus Ibsen
   draft: false
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388806859
 
 

 ##########
 File path: 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.
 
 Review comment:
   ```suggestion
   The Apache Camel project is moving to release schedule with Long Term Support (LTS) and non-LTS releases.
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388809026

Review comment:
```suggestion
but our LTS is limited to a 1-year schedule (typically same timeframe for Camel 2.x).
```

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388808314

Review comment:
```suggestion
For non-LTS releases then we plan to not release patch releases. For example, there will
```

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

With regards,
Apache Git Services

[GitHub] [camel-website] zregvart commented on a change in pull request #166: Blog post about LTS and release schedule

Posted by GitBox <gi...@apache.org>.

zregvart commented on a change in pull request #166: Blog post about LTS and release schedule
URL: https://github.com/apache/camel-website/pull/166#discussion_r388806635
 
 

 ##########
 File path: 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).
 
 Review comment:
   ```suggestion
   This allows the Camel project to innovate and move much faster in non-LTS releases.
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services